Repository navigation
Clean up Reference annotations that drifted - #163902
rust-bors[bot] merged 1 commit into
Conversation
This comment was marked as resolved.
This comment was marked as resolved.
The Reference warns when a `//@ reference:` annotation points to a rule that isn't in the Reference. Some of these had accumulated. Let's clean them up.
e1bf4fe to
879c65a
Compare
There was a problem hiding this comment.
Thanks @traviscross. This looks good.
I had a thought on something we could improve while we're here or on another PR.
|
Some changes occurred in coverage tests. cc @Zalathar |
|
@bors r=PLeVasseur,traviscross rollup |
|
Can we gate CI on these being correct? It seems unfortunate that having the links be wrong causes only warnings. |
Agreed it's unfortunate, but I don't know how we could gate CI at the moment. These identifiers change on the Reference side. We wouldn't want people to need to fix the tests in unrelated Rust PRs to get those PRs to merge. |
|
The way we do that with other subtrees/submodules is that the discrepancies get fixed in sync PRs. So the person doing a sync from the reference repo into |
|
Thanks; makes sense. Will think about that. Our syncs are fairly automated (which we rely on in various ways), so that could be one hurdle. |
…ations_cleanup-drift, r=PLeVasseur,traviscross Clean up Reference annotations that drifted The Reference warns when a `//@ reference:` annotation points to a rule that isn't in the Reference. Some of these had accumulated. Let's clean them up. r? @PLeVasseur cc @DanielEScherzer (As work within the scope of the lang-docs team, this falls outside the scope of the `forge#1040` policy; nonetheless, I'll note that this work was done with the assistance of AI tools and that this has been prearranged with all reviewers.)
…ations_cleanup-drift, r=PLeVasseur,traviscross Clean up Reference annotations that drifted The Reference warns when a `//@ reference:` annotation points to a rule that isn't in the Reference. Some of these had accumulated. Let's clean them up. r? @PLeVasseur cc @DanielEScherzer (As work within the scope of the lang-docs team, this falls outside the scope of the `forge#1040` policy; nonetheless, I'll note that this work was done with the assistance of AI tools and that this has been prearranged with all reviewers.)
…uwer Rollup of 16 pull requests Successful merges: - #163887 (Remove `NonOwner` variant from `AstOwner`) - #163892 (add revisions for `pass -> [err|ICE]` ui tests `-Znext-solver` ) - #162156 (add IBM f128 type) - #163925 (Submodule update of rustc-perf) - #163658 ([PAC] Stop hard coding key and discriminator, consult schema instead) - #163854 (Include offset in the alignment check when creating ConstValue::Indirect in GVN) - #163874 (explicitly check for fresh vars in canonicalize) - #163880 (Don't add pkgs.rustc to PATH in nix dev shell) - #163893 (Panic on `StableHash` of a `Path` with `GenericArgs`) - #163894 (revisions for TAIT in env bug) - #163902 (Clean up Reference annotations that drifted) - #163905 (Remove redundant closure in bootstrap) - #163921 (abby DSL: implement ambiguity) - #163927 (abby DSL: change `where` syntax to `predicates`) - #163933 (Add `synchronization` import lib to windows-gnullvm dist) - #163937 (Abby test DSL: dont ICE on foralls with unused bound vars) > [!WARNING] > This rollup conflicts with pending auto build #163934 and may need to be recreated if the pending build succeeds.
Rollup merge of #163902 - traviscross:TC/add-reference-annotations_cleanup-drift, r=PLeVasseur,traviscross Clean up Reference annotations that drifted The Reference warns when a `//@ reference:` annotation points to a rule that isn't in the Reference. Some of these had accumulated. Let's clean them up. r? @PLeVasseur cc @DanielEScherzer (As work within the scope of the lang-docs team, this falls outside the scope of the `forge#1040` policy; nonetheless, I'll note that this work was done with the assistance of AI tools and that this has been prearranged with all reviewers.)
…uwer Rollup of 16 pull requests Successful merges: - rust-lang/rust#163887 (Remove `NonOwner` variant from `AstOwner`) - rust-lang/rust#163892 (add revisions for `pass -> [err|ICE]` ui tests `-Znext-solver` ) - rust-lang/rust#162156 (add IBM f128 type) - rust-lang/rust#163925 (Submodule update of rustc-perf) - rust-lang/rust#163658 ([PAC] Stop hard coding key and discriminator, consult schema instead) - rust-lang/rust#163854 (Include offset in the alignment check when creating ConstValue::Indirect in GVN) - rust-lang/rust#163874 (explicitly check for fresh vars in canonicalize) - rust-lang/rust#163880 (Don't add pkgs.rustc to PATH in nix dev shell) - rust-lang/rust#163893 (Panic on `StableHash` of a `Path` with `GenericArgs`) - rust-lang/rust#163894 (revisions for TAIT in env bug) - rust-lang/rust#163902 (Clean up Reference annotations that drifted) - rust-lang/rust#163905 (Remove redundant closure in bootstrap) - rust-lang/rust#163921 (abby DSL: implement ambiguity) - rust-lang/rust#163927 (abby DSL: change `where` syntax to `predicates`) - rust-lang/rust#163933 (Add `synchronization` import lib to windows-gnullvm dist) - rust-lang/rust#163937 (Abby test DSL: dont ICE on foralls with unused bound vars) > [!WARNING] > This rollup conflicts with pending auto build #163934 and may need to be recreated if the pending build succeeds.
…uwer Rollup of 16 pull requests Successful merges: - rust-lang/rust#163887 (Remove `NonOwner` variant from `AstOwner`) - rust-lang/rust#163892 (add revisions for `pass -> [err|ICE]` ui tests `-Znext-solver` ) - rust-lang/rust#162156 (add IBM f128 type) - rust-lang/rust#163925 (Submodule update of rustc-perf) - rust-lang/rust#163658 ([PAC] Stop hard coding key and discriminator, consult schema instead) - rust-lang/rust#163854 (Include offset in the alignment check when creating ConstValue::Indirect in GVN) - rust-lang/rust#163874 (explicitly check for fresh vars in canonicalize) - rust-lang/rust#163880 (Don't add pkgs.rustc to PATH in nix dev shell) - rust-lang/rust#163893 (Panic on `StableHash` of a `Path` with `GenericArgs`) - rust-lang/rust#163894 (revisions for TAIT in env bug) - rust-lang/rust#163902 (Clean up Reference annotations that drifted) - rust-lang/rust#163905 (Remove redundant closure in bootstrap) - rust-lang/rust#163921 (abby DSL: implement ambiguity) - rust-lang/rust#163927 (abby DSL: change `where` syntax to `predicates`) - rust-lang/rust#163933 (Add `synchronization` import lib to windows-gnullvm dist) - rust-lang/rust#163937 (Abby test DSL: dont ICE on foralls with unused bound vars) > [!WARNING] > This rollup conflicts with pending auto build #163934 and may need to be recreated if the pending build succeeds.
…uwer Rollup of 16 pull requests Successful merges: - rust-lang/rust#163887 (Remove `NonOwner` variant from `AstOwner`) - rust-lang/rust#163892 (add revisions for `pass -> [err|ICE]` ui tests `-Znext-solver` ) - rust-lang/rust#162156 (add IBM f128 type) - rust-lang/rust#163925 (Submodule update of rustc-perf) - rust-lang/rust#163658 ([PAC] Stop hard coding key and discriminator, consult schema instead) - rust-lang/rust#163854 (Include offset in the alignment check when creating ConstValue::Indirect in GVN) - rust-lang/rust#163874 (explicitly check for fresh vars in canonicalize) - rust-lang/rust#163880 (Don't add pkgs.rustc to PATH in nix dev shell) - rust-lang/rust#163893 (Panic on `StableHash` of a `Path` with `GenericArgs`) - rust-lang/rust#163894 (revisions for TAIT in env bug) - rust-lang/rust#163902 (Clean up Reference annotations that drifted) - rust-lang/rust#163905 (Remove redundant closure in bootstrap) - rust-lang/rust#163921 (abby DSL: implement ambiguity) - rust-lang/rust#163927 (abby DSL: change `where` syntax to `predicates`) - rust-lang/rust#163933 (Add `synchronization` import lib to windows-gnullvm dist) - rust-lang/rust#163937 (Abby test DSL: dont ICE on foralls with unused bound vars) > [!WARNING] > This rollup conflicts with pending auto build #163934 and may need to be recreated if the pending build succeeds.
The Reference warns when a
//@ reference:annotation points to a rule that isn't in the Reference. Some of these had accumulated. Let's clean them up.r? @PLeVasseur
cc @DanielEScherzer
(As work within the scope of the lang-docs team, this falls outside the scope of the
forge#1040policy; nonetheless, I'll note that this work was done with the assistance of AI tools and that this has been prearranged with all reviewers.)