Hans Elias J.

We actually have started working on some better docs at https://rustler-web.onrender.com/docs. Specifically there is a very early WIP type mapping cheat sheet at https://rustler-web.onrender.com/docs/cheat-sheet. @Qqwy Really nice summary, maybe it...

This isn't really a bug, this is intended behavior. We could add another iterator type which returns an enum for either an element or an improper tail.

Not much we can do about this I believe. An alternative would be to introduce a new printing function in rustler that uses the BEAM provided printing functions. Relevant: https://github.com/rusterlium/rustler/issues/72

There is this, which could enable us to change where the default rust print functions send their outputs. This seems to be what the rust test framework uses. The issue...

I like the idea here, but I think dynamic `load_data` should be a separate argument, something like `load_data_fun`? As is, this will break existing `load_data`s that are atom pairs.

Would you mind sending me the test project?

It seems like the problem with having the :phoenix and :gettext compilers before rustler is that they seem to load modules in the user code. This causes the NIF to...

While it is true that Serde wasn't what I thought of when I opened this issue, @cgregfreeman does have a valid point. Serde has established a very well understood and...

Ah, I was not aware serde was doing it that way. Don't really like it, but it solves the problem at least. So as far as I can see there...

If we supported the serde traits, it would enable the user to use serde's mechanism for remote structs. But again, that's not completely optimal either. We should probably support something...