Magnus

Making the error readable: ```elixir path = {{ :nocatch, { :dialyzer_error, [78, 111, 116, 32, 97, 32, 114, 101, 103, 117, 108, 97, 114, 32, 102, 105, 108, 101, 58,...

The error is thrown within this function in `dialyzer_plt.erl`: ```erlang compute_md5_from_file(File) -> case beam_lib:all_chunks(File) of {ok, _, Chunks} -> %% We cannot use beam_lib:md5 because it does not consider %%...

> Thanks for investigating! I think we need to handle any {:dialyzer_error, binary()} by printing the binary as an error and then halt the VM with a non-zero. Yes, that...

@filmor should we pick this PR up again? Can I somehow help to move it along?

> As a first step, I'll rebase it. Maybe we could have a call on this to talk about the next steps? Yep, lets do that.

I think rustler_mix fails to recompile on changed `MIX_ENV`, it only considers changes to source files IIRC. We will need to cache that information and recompile on changes. To work...

I can reproduce this with https://github.com/evnu/rustler_bug_switch_profile.

By default, `Rustler.Config` retrieves the build mode from `Mix.env()` ([here](https://github.com/rusterlium/rustler/blob/1ec2923bdd60713132e48b596699dc04ca58b4b9/rustler_mix/lib/rustler/compiler/config.ex)). As noted before, this can be overridden in the `use` macro. But changing the build mode with `MIX_ENV` does not...

> Is the AddStruct module supposed to be automatically created in the Elixir side, or is that left up to the user? That is left up to the user.

Note that the same atom (eg `hello`) could be represented by a different number for different invocations of the VM. Then, the hash for the same atom would also be...