Paul Schoenfelder

I think you make good points @secretworry. I've converted over to using the non-bang versions anyway due to this behavior, though I think it still potentially could throw people off...

I Think #35 solves the issue of users not being able to add new fields to `conn`.

This should be fairly easy to implement, but I think there are some associated changes involved as well. Namely deprecating `get_resp_body/2`, as it won't work with this change, and I...

Yeah that's more or less what I recommend when people ask about it, but was hoping it might be easier in the case of Rust, not that building in Docker...

@scrogson The problem with shipping pre-compiled binaries is that you have to have a binary compiled for each architecture the package might be used on, which isn't practical when you...

Makes sense :). I like the idea of putting control in the library author's hands to generate binaries for a preset list of architectures, but I think it would also...

Sure, today, it basically works like this (assuming NIFs are part of the equation): - Grab a copy of ERTS from a machine running on the desired target architecture, this...

My understanding is that you just need to make sure that when the rust compiler is called when building your project, that it gets passed the appropriate cross-compilation flags to...

Definitely an issue we'll want to address. One of the reasons we're using `sbcast` is because we want the guarantee that when it returns, we know that all of the...

This is a great idea, though it would require some significant changes. I'll definitely consider it if there is enough feedback in favor of it.