plonky2/Cargo.toml

[workspace]
members = ["evm", "field", "maybe_rayon", "plonky2", "starky", "util"]
resolver = "2"

[profile.release]
opt-level = 3
incremental = true
#lto = "fat"
#codegen-units = 1

[profile.bench]
opt-level = 3

[patch.crates-io]
plonky2_evm = { path = "evm" }
plonky2_field = { path = "field" }
plonky2_maybe_rayon = { path = "maybe_rayon" }
plonky2 = { path = "plonky2" }
starky = { path = "starky" }
plonky2_util = { path = "util" }
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			`[workspace]`
Move ecdsa to its own repo 2023-03-03 16:12:40 -08:00			`members = ["evm", "field", "maybe_rayon", "plonky2", "starky", "util"]`
Fix resolver warning When running eg `cargo check` or `cargo build` you got greeted with the following warning: ``` warning: some crates are on edition 2021 which defaults to `resolver = "2"`, but virtual workspaces default to `resolver = "1"` note: to keep the current resolver, specify `workspace.resolver = "1"` in the workspace root's manifest note: to use the edition 2021 resolver, specify `workspace.resolver = "2"` in the workspace root's manifest ``` This PR fixes this. 2023-07-13 12:21:40 +08:00			`resolver = "2"`
Move profile defns to root workspace toml. (#437) 2022-01-18 11:41:08 +11:00
			`[profile.release]`
			`opt-level = 3`
Incremental release builds Since it's a library, in practice release builds are used for slower tests, not for a binary that needs to be reproducible. 2023-04-12 07:34:17 -07:00			`incremental = true`
Move profile defns to root workspace toml. (#437) 2022-01-18 11:41:08 +11:00			`#lto = "fat"`
			`#codegen-units = 1`

			`[profile.bench]`
			`opt-level = 3`
Add patch section to workspace config file 2023-02-02 18:12:22 -05:00
			`[patch.crates-io]`
			`plonky2_evm = { path = "evm" }`
			`plonky2_field = { path = "field" }`
			`plonky2_maybe_rayon = { path = "maybe_rayon" }`
			`plonky2 = { path = "plonky2" }`
			`starky = { path = "starky" }`
			`plonky2_util = { path = "util" }`