Brian Anderson

Thanks for the suggestion. Since this is partially a teaching tool, and for simplicity sake, I'm inclined not to cache files and leave it up to the OS's own page...

In addition to knowing which features are on, I think it would be useful to know which features are off too. Let me see the entire "feature-space". e.g. for @psinghal20's...

@dtolnay I took a stab at a patch, but unfortunately it's complicated to do in-tree because implementing `Drop` makes it impossible to destructure `Value`. Here's my branch anyway: https://github.com/brson/json/tree/drop And...

Here's a selection of the build errors that happen when adding `Drop`: ``` | ------------------------------------------ in this macro invocation error[E0509]: cannot move out of type `value::Value`, which implements the `Drop`...

@dtolnay Having that code in-tree would be marginally better than not just because it would be upstream. I'd still root my `Value` in a wrapper type on my end to...

Hm, well actually, having that by-value drop would probably just make it harder to implement the wrapper type downstream, because then the wrapper has to use a RefCell or something...

> I think it would be possible to build a Rust-only OS X SDK that's redistributable since it doesn't need header files, which would make this a lot easier. This...

> This does seem possible, and would be cool, as long as you never need to build any C code. There may even be clean-room redeclarations of various core Darwin...

@tarcieri no I just need something easy and as foolproof as reasonable. I spent the last bit switching to ecdsa with the k256 crate, and it seems to avoid the...

@isislovecruft This is how I had ed25519-dalek configured in Cargo.toml: ``` ed25519-dalek = { version = "1.0.1", default-features = false, features = ["u64_backend"] } ``` The target was Solana's bpf...