You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Integrated into cargo or separate rustup component like clippy?
How does the process for making new rustdoc JSON formats work w.r.t. cargo-semver-checks merged into cargo?
PRs to rust-lang/rust run submodule test suites, like cargo's. Presumably they would test the merged cargo-semver-checks as well.
If a PR to rust-lang/rust emits a new rustdoc JSON format version, cargo-semver-checks would need to be updated to support it.
That appears to be a chicken-and-egg problem: the PR won't pass, so no new versions of rustdoc-types will exist, so no new cargo-semver-checks -> cycle.
Blockers
--explainflag for lints #49--base-versionargument #50--base-git <repo>argument #51--base-manifest-path <path>argument #52--workspace,--package,--excludeflags #53-Zflag #54--all-featuresexposes APIs in an unstable feature #321 for context)Nice-to-haves
Open questions
cargoor separate rustup component like clippy?rust-lang/rustrun submodule test suites, like cargo's. Presumably they would test the mergedcargo-semver-checksas well.rust-lang/rustemits a new rustdoc JSON format version,cargo-semver-checkswould need to be updated to support it.rustdoc-typeswill exist, so no newcargo-semver-checks-> cycle.Things to remove
_is hidden (blocked on private/hidden features rust-lang/cargo#10882)bench,nostd,no_std,private,unstable,unstable[-_].*,nightly(blocked on private/hidden features rust-lang/cargo#10882, stable/unstable/nightly-only features rust-lang/cargo#10881)--default-features,--only-explicit-featuresMerge Proposal (example):
Motivation
Drawbacks
Behavior
Alternatives
Prior Art
Future Possibilities