sezaru
In my project, I have a compile-time code that can generate some warning depending on some circumstances.
To show the warning I do IO.warn(“…”).
The problem is that, with this, the compiler will happily continue even if I add –warning-as-errors option.
Shouldn’t that option make the compiler fail in this case or am I missing something here?
Trending in Questions
Hi all,
I’m working on a Phoenix project where I need to make external HTTP requests and I’m trying to choose between Req and HTTPoison....
New
I’m very new to Elixir, so sorry if this is a silly question:
I am wondering what happens to the mailbox of a process when the machine i...
New
Hello everyone!
I am new to coding with Elixir/Erlang. And i am looking for some utilities for fuzzing testing like AFL++.
Does anyone ...
New
How do I tell Hologram not to escape HTML when substituting into templates?
{Textile.render(@product.long_description)}
escapes the HTM...
New
Background
When trying to execute mix release on a Windows 11 machine for a Phoenix project I get the following error:
* assembling mark...
New
I’d like to create a file with 600 permissions (rw-------), but there’s a race condition if I create it and then change the permissions. ...
New
Is there a way to import record definitions in the iex shell for pretty printing (similar to the rr command in the erl shell)? This woul...
New
Other Trending Topics
Hey there,
I haven’t seen a list of useful Elixir specific skills for the popular AI tools yet so I’m starting one here with my first.
...
New
Hi everyone :waving_hand:
I wanted to share something I’ve been building — NowBlind, a random chat app designed to help people discover ...
New
I fully migrated to my own harness from Anthropic/Gemini and I think it’s time to share it. Welcome DSH, the DeepSeek Harness, fully writ...
New
(I just needed to vent somewhere and LinkedIn is full of hope, or hype, I’m not sure which exactly)
AI dream has many faces, but general...
New
Localize is the next generation localisation library for Elixir. Think of it as ex_cldr version 3.0. The first version will be released ...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #code-sync
- #discussion
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #ai
- #elixirconf-us
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #blog-post
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #security
- #elixirconf-eu
- #processes
- #api
- #forms
- #hex










Showing Posts 1 to 7- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
garrison
The docs kinda imply that only
warn/2emits the diagnostic and notwarn/1, which seems like an unfortunate overloading of the function name to me.al2o3cr
FWIW,
IO.warn/1directly callsIO.warn/2:https://github.com/elixir-lang/elixir/blob/4a8d4f29ae7dd238d29f8a1a7d9607d23c3550d0/lib/elixir/lib/io.ex#L444-L447
@sezaru - long shot, but is it possible you’re running into something weird from the tail-call optimization mentioned in the docs for
IO.warn/1?sezaru
Actually, the code that generates the warning is from AshGraphql, I just didn’t add that before because I thought it was unnecessary. But either way that code is run at compile time for the resource I’m creating, so I think it should count as “my code” and not as “dependency code”.
I also tried adding some other warnings to see if it would stop the compiler but they didn’t, basically I tried this:
which generated the following warnings:
As you can see, the warnings show up during compilation, but the compilation itself finished without any errors.
Btw, I’m using Elixir 1.19.1
garrison
Oh so it does, never mind then! Usually when functions of different arity share behavior it’s mentioned in the docs (e.g. this one in the same module) so that threw me off.
sezaru
Yeah.. I don’t get this, I tried a lot of different warnings and projects, I also tried with Elixir 1.18 and I still can’t make
--warnings-as-errorswork at all.I’m just not sure if this is actually a bug or just something else that I’m missing because I’m confident that if it was really not working for everyone, then this would be already reported tbh.
Does this option works for you guys? If so, do you mind giving me a code snippet that generates a warning that should be triggered as an error when using this option for me to try it?
Gazler
In this example, you have used
--warning-as-errorsand not--warnings-as-errorssezaru
Dear god, I can’t believe that was it…
