CodesInChaos

Are there any type macros in the standard library already?

For montgomery form Curve25519 you can use `MontgomeryCurve25519.GetPublicKey`. Use a random 32 byte value as private key. _Note that this twiddles some bits to match NaCl, so it doesn't work...

``` byte[] publicKey, privateKey; Ed25519.KeyPairFromSeed(out publicKey, out privateKey, GetRandomBytes(32)); byte[] signature = Ed25519.Sign(message, privateKey); bool isValid = Ed25519.Verify(signature, message, publicKey); ```

Looks pretty cool, but unfortunately it's unlikely that I'll get to integrate it any time soon. - The biggest issue is that this code is BSD licensed, whereas I'd like...

My main problem is that I can't figure out how I want the API to look like. With issues like: - Single responsibility principle and flexibility vs. an integrated approach...

No, this is unrelated to John Hauser's SoftFloat. I needed high performance deterministic floats for a now abandoned project, so this project is on hold as well. Some key differences:...

At minimum you'd have to replace all `std::` imports by `core::` and `alloc::`. Additional challenges: * `std::io::{Read, Error, Write}` -- Not in `alloc` * implementing `std::Error` -- Can probably be...

@danielpclark The usual workaround is returning the original value as part of the error.

Not sure if it still applies to the current version of `bytes`. You can either hope it was fixed by unrelated changes, or reproduce it in 0.4.12, figure out why...

@abonander Taking the second bytes by reference would remove the need to return it in the error case. @DoumanAsh > Shouldn't you be able to do similar thing by converting...