Stephen Touset

Are there any plans to cut a release with this PR? `annotate_routes` doesn't work on Rails 6.2.

Is this dead? Having Draper blow away preloaded associations is a massive hit to performance.

I'm definitely interested, but it's not something I'd want to pull the trigger on without some consideration. I can't imagine it doesn't include unsafe code (e.g., to call things like...

There's a bit of benefit here in that we don't have to provide any libsodium bindings, but I'm a bit on the fence as to whether or not that warrants...

This doesn't really remove `unsafe`, it just kicks the can to the `region-rs` crate which itself uses `unsafe` to call operating system APIs like `mprotect`.

`std::io::Stdin` implments the `Read` trait, so you can read raw bytes from it into a provided buffer (such as that returned by `secret.borrow_mut()`). That's not the *most* useful thing right...

Yep. [`sodium_mshield`](https://github.com/jedisct1/libsodium/blob/master/src/libsodium/include/sodium/utils.h#L162) was added to libsodium in a [recent commit](https://github.com/jedisct1/libsodium/commit/bfeca0eb73c1650fa17a3b0f5e845e95f28516a4) but has yet to be released. When it is, I'll incorporate it.

I tried to merge two runs using the `cfg` flag on and off, and the coverage report would only ever show one or the other was hit. I followed the...

I don't have a minimal test-case for the first paragraph above yet. I'm neck-deep in some stuff, will try to get you one.

This has bitten me as well. The "obvious" fix is to change the logic to link to `rustup` with symlinks rather than hardlinks, since symlinks-to-symlinks have well-defined semantics (unlike hardlinks-to-symlinks)....