3 Commits

Author	SHA1	Message	Date
Daniel Lubarov	3346d3f902	field_types -> types (#583) ... * `field_types` -> `types` Here too, I think "field" is usually clear from context, e.g. in `use plonky2::field::types::Field;`. * fixes * fmt	2022-06-27 12:24:09 -07:00
Remco Bloemen	7769c269bf	Do not export global allocator (#533) ... * Do not export allocator * Make sure to use jemalloc in all downstream tests * Update readme * Remove test jemalloc boilerplate * One more * Fix clippies * One more * Clippy Co-authored-by: Daniel Lubarov <daniel@lubarov.com>	2022-05-03 13:16:53 -07:00
Daniel Lubarov	7d6c0a448d	Halo2 style lookup arguments in System Zero (#513) ... * Halo2 style lookup arguments in System Zero It's a really nice and simple protocol, particularly for the verifier since the constraints are trivial (aside from the underlying batched permutation checks, which we already support). See the [Halo2 book](https://zcash.github.io/halo2/design/proving-system/lookup.html) and this [talk](https://www.youtube.com/watch?v=YlTt12s7vGE&t=5237s) by @daira. Previously we generated the whole trace in row-wise form, but it's much more efficient to generate these "permuted" columns column-wise. So I changed our STARK framework to accept the trace in column-wise form. STARK impls now have the flexibility to do some generation row-wise and some column-wise (without extra costs; there's a single transpose as before). * sorting * fixes * PR feedback * into_iter * timing	2022-03-16 17:37:34 -07:00