bnjbvr commented on Issue #956:
ping @fitzgen, any updates about this idea?
fitzgen commented on Issue #956:
We did this in wasmtime. Still +1 for doing it here too.
Happy to make a PR if others are on board!
bnjbvr labeled Issue #956:
While there isn't really One True Way to organize a workspace and the crates within it that is adopted by a majority of the rust ecosystem, of the different ways to do it, the most prevalent convention I've seen is:
- to have the main, public facing crate in the root of the repo (ie the
cranelift
crate)- for all sub crates
cranelift-foo
, put them atcrates/foo
For example, both
cargo
andwasm-bindgen
follow this convention.How do folks feel about switching to this layout?
See also https://github.com/CraneStation/wasmtime/pull/305 for this same thing for wasmtime.
bnjbvr commented on Issue #956:
I realize that my fuzzy-search auto-complete tooling in terminals will be less effective, if we did this. Currently, I can type "gen" for "cranelift-codegen", but with the additional "crates" directory, I won't be able to do this. It's a minor annoyance, if there was a way to fix it (use special paths for Cargo.toml files and the src directory they refer to?) it'd be nice, otherwise i can live with it.
alexcrichton transferred Issue #956:
While there isn't really One True Way to organize a workspace and the crates within it that is adopted by a majority of the rust ecosystem, of the different ways to do it, the most prevalent convention I've seen is:
- to have the main, public facing crate in the root of the repo (ie the
cranelift
crate)- for all sub crates
cranelift-foo
, put them atcrates/foo
For example, both
cargo
andwasm-bindgen
follow this convention.How do folks feel about switching to this layout?
See also https://github.com/CraneStation/wasmtime/pull/305 for this same thing for wasmtime.
Last updated: Dec 23 2024 at 13:07 UTC