Why is not compilation aborted when an undefined module attribute is found?

[Exadra37]

@al2o3cr

Some historical digging reveals that it used to; around the time of Elixir 1.4 that was changed, by commits like:

https://github.com/elixir-lang/elixir/commit/bc2480d53749ffbd102898f5ead7e0948aa860aehttps://github.com/elixir-lang/elixir/commit/bc2480d53749ffbd102898f5ead7e0948aa860ae

I really don’t understand the rational of allowing this breaking change and not allowing the breaking change that would really fix the issue and make Elixir compilation to deliver a more robust code, instead of buggy code as it does at the moment.

@hst337

Elixir’s code states that it is a known issue and they just don’t want to add breaking change

        # TODO: Consider raising instead of warning on v2.0 as it usually cascades

The rationale of postponing for v2.0 really puzzles me, because that version may never exist as Jose keeps saying, but even if it was scheduled it doesn’t make any sense in my mind to wait, because this is a compiler bug that should be fixed, because a compiler that produces bad code output isn’t helping anyone.