José Valim
José Valim
We should fix this in mix indeed. Thank you for the report!
This is beautiful! 😍 Although not related to this issue, but for completeness, I have one last to do in relation to the `erl_prim_loader` and archives which is to remove...
I have to rewrite this part of the code... so I will look into this (there is already some work in progress in here too).
:+1: for moving it out but we most likely always want to run this, as mentioned by @maennchen.
The protocol error is caused by an incorrect assumption in a library, it is fixed here: https://github.com/asummers/erlex/pull/60 The additional warnings are related to opaqueness in Erlang/OTP 28. @sabiwara, we discussed...
@sabiwara I looked [at the source code](https://github.com/erlang/otp/blob/f5af4de0c4246c9425b99843233a6bc662046038/lib/dialyzer/src/dialyzer_contracts.erl#L913), and this warning comes when checking the contracts of functions, there is no longer AST information attached with it (and, even if it...
`no_opaque` may be a bit too broad but it seems we have no other option.
The inspect one seems to be an Elixir bug. The opaqueness ones require this: https://github.com/elixir-lang/elixir/issues/14837#issuecomment-3419685325
Btw, we will likely have a fix for this in Erlang/OTP 28.1, so stay on 27 until 28.1 is out and you may be able to upgrade without issues.
It requires a new Elixir version.