Jeff Burdges

We need to open up the hash-to-curve anyweays because the IRTF draft permits user specified xofs, everyone hates the sha2 xmd, some curves require other xofs, and our code currently...

I guess my last question is answered here: https://github.com/arkworks-rs/curves/pull/76

`Into` is purely a convenience, so if you've manually prepared `d_prepared` then you can manually prepare the `c`. It's hard to share `d_prepared` between verifications anyways right now. We'll need...

I donno all the commitment schemes, but one pattern would be you make the commitment and opening proof normally, but output additional metadata for the zk opener. You then have...

Arkworks' hash-to-curve interface seems kinda fucked too by not exposing XoFs correctly. I've started a PR but it'll stay impressionistic and need work by someone else. Also this duplicates #5...

Appears allocators are not completely sorted out in Rust yet anyways https://github.com/rust-lang/rfcs/issues/538 although maybe that does not matter here.

I'd think a `mut` prefix works fine without the `let`, like in function arguments. Another [proposed](https://github.com/rust-lang/rfcs/pull/1546#issuecomment-284634326) was `trait Foo { struct { f: T, g: U } ... }`, but...

You could use `ref` and `ref mut` since this represents some sort of indirection, but.. We should not use syntax that might confuse people just learning the borrowing dance, so...

I suspect Niko's custom disjointness rules [favor](https://github.com/nikomatsakis/fields-in-traits-rfc/issues/16#issuecomment-304158769) using `struct`, or at least using braces to express disjointness, because multiple `struct` field declaration can produce different families of disjoint fields, and...

Would more finer-grained disjointness rules be expressed by grouping or something else? If grouping, then you could omit the `struct` key word, use the existing `,` version, but eventually let...