What valid code can refer to non-existing module attribute?
hst337
dimitarvp
Eh, I forgot what I even had in mind back then. Main point was to allow --warnings-as-errors to propagate to dependencies as well as our own code. No clue how was that even related to non-compilable code (like a module attribute missing but being referenced to). 
1
zachallaun
I’m confused. You had an issue and a solution was posed (use warnings-as-errors flag). You thought it wouldn’t work, but then were informed that it would work as warnings in dependencies don’t halt compilation.
So, problem solved, yes?
Re: why behavior was changed in the past: it was Elixir 1.4, we’re now officially on 1.14. My guess is that the core team’s opinions on maintaining a stable environment have changed in the last 5+ years as adoption had increased. Also, the behavior that was changed was the behavior of an opt-in option, not a default, so the impacted group was more clear-cut and well defined.
0
Exadra37
Not a solution… at best a work-around and the problem persists for non informed developers.
0