plonky2/util/Cargo.toml

[package]
name = "plonky2_util"
description = "Utilities used by Plonky2"
version = "0.1.0"
edition = "2021"

[dependencies]
Split into crates (#406) * Split into crates I kept other changes to a minimum, so 95% of this is just moving things. One complication that came up is that since `PrimeField` is now outside the plonky2 crate, these two impls now conflict: ``` impl<F: PrimeField> From<HashOut<F>> for Vec<u8> { ... } impl<F: PrimeField> From<HashOut<F>> for Vec<F> { ... } ``` with this note: ``` note: upstream crates may add a new impl of trait `plonky2_field::field_types::PrimeField` for type `u8` in future versions ``` I worked around this by adding a `GenericHashOut` trait with methods like `to_bytes()` instead of overloading `From`/`Into`. Personally I prefer the explicitness anyway. * Move out permutation network stuff also * Fix imports * Fix import * Also move out insertion * Comment * fmt * PR feedback 2021-12-28 11:51:13 -08:00			`[package]`
			`name = "plonky2_util"`
metadata 2022-01-21 10:14:44 -08:00			`description = "Utilities used by Plonky2"`
Split into crates (#406) * Split into crates I kept other changes to a minimum, so 95% of this is just moving things. One complication that came up is that since `PrimeField` is now outside the plonky2 crate, these two impls now conflict: ``` impl<F: PrimeField> From<HashOut<F>> for Vec<u8> { ... } impl<F: PrimeField> From<HashOut<F>> for Vec<F> { ... } ``` with this note: ``` note: upstream crates may add a new impl of trait `plonky2_field::field_types::PrimeField` for type `u8` in future versions ``` I worked around this by adding a `GenericHashOut` trait with methods like `to_bytes()` instead of overloading `From`/`Into`. Personally I prefer the explicitness anyway. * Move out permutation network stuff also * Fix imports * Fix import * Also move out insertion * Comment * fmt * PR feedback 2021-12-28 11:51:13 -08:00			`version = "0.1.0"`
			`edition = "2021"`

			`[dependencies]`