Weihang Lo
Weihang Lo
> I think we can just exclude it from the workspace, or bump MSRV if necessary because 1.40 is ancient by now. 7d391035aa7a931ce5e559e17f090e2c94dc6fea fixes it, but I tend to do...
@Shnatsel are you good with 1.64? It appears that workspace inheritance was stabilized in 1.64. https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#workspace-inheritance
Feel free to merge this as-is if is preferred.
It would also help if the version info of the Rust toolchain is provided. The output of `cargo -vV` should be sufficient.
I am going to close this, as there is no action needed. See [the updated PR description](https://github.com/rust-lang/cargo/issues/14655#issue-2573600377) that provides some solutions if you're stuck.
@Kelvin-1013 please don't post unrelated cryptocurrency ads here
@Linyxus please read the maintainer's note in the PR description.
That is a good suggestion! The function checking it resides [here](https://github.com/rust-lang/cargo/blob/bffece899e9ba3cf948c9498713ba7fbc4ec10e4/src/cargo/ops/mod.rs#L78). I think we can either expand the error message, or add an extra error context such as “failed to...
> Why only for the workspaces? Doesn't it make sense to do it for the non-workspace publish too? See https://github.com/rust-lang/cargo/issues/13397#issuecomment-3336450116 This PR is a proof-of-concept not meant for general discussions...
Originally posted at . Here is a result of a performance benchmark that mostly tests the rustc part. * It adds `[email protected]` as a dependency and runs `cargo clean &&...