-
Notifications
You must be signed in to change notification settings - Fork 12.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enforce the static symbol order. #74203
Enforce the static symbol order. #74203
Conversation
@bors rollup=always |
This will need rebasing after #74175 lands, but the code is reviewable in its current state. |
@bors r+ |
@bors r=petrochenkov |
📌 Commit 714b6ec has been approved by |
…rder, r=petrochenkov Enforce the static symbol order. By making the proc macro abort if any symbols are out of order. The commit also changes the proc macro collect multiple errors (of order or duplicated symbols) and prints them at the end, which is useful if you have multiple errors. r? @petrochenkov
If #72920 lands first this will need to be updated |
☔ The latest upstream changes (presumably #74175) made this pull request unmergeable. Please resolve the merge conflicts. |
714b6ec
to
b82df91
Compare
I rebased. @bors r=petrochenkov |
📌 Commit b82df9188868efef5366699826dbeb3585f0e098 has been approved by |
☔ The latest upstream changes (presumably #74214) made this pull request unmergeable. Please resolve the merge conflicts. |
b82df91
to
264797a
Compare
I rebased again. @bors r=petrochenkov |
📌 Commit 264797aeabe927a56d28466f3f1939aa50765274 has been approved by |
🌲 The tree is currently closed for pull requests below priority 5, this pull request will be tested once the tree is reopened |
☔ The latest upstream changes (presumably #74375) made this pull request unmergeable. Please resolve the merge conflicts. |
By making the proc macro abort if any symbols are out of order. The commit also changes the proc macro collect multiple errors (of order or duplicated symbols) and prints them at the end, which is useful if you have multiple errors.
Because it represents the symbol `ItemContext`, and `sym` identifiers are supposed to match the actual symbol whenever possible.
264797a
to
600b824
Compare
I rebased yet again. This commit is super conflict-prone. @bors r=petrochenkov |
📌 Commit 600b824 has been approved by |
🌲 The tree is currently closed for pull requests below priority 5, this pull request will be tested once the tree is reopened |
@bors p=1 |
How do p=1 and rollup=always interact? |
…arth Rollup of 7 pull requests Successful merges: - rust-lang#73421 (Clarify effect of orphan rule changes on From/Into) - rust-lang#74037 (Update reference to CONTRIBUTING.md) - rust-lang#74203 (Enforce the static symbol order.) - rust-lang#74295 (Add and fix BTreeMap comments) - rust-lang#74352 (Use local links in the alloc docs.) - rust-lang#74377 (Move libstd's default feature to libtest) - rust-lang#74381 (Update docs for str::as_bytes_mut.) Failed merges: r? @ghost
@nnethercote sort order is by priority first, then rollupability. It's fine to p=1 rollup=always, it means that the PR is high priority but you also have a strong expectation that it will not break anything and encourage rollup authors to pick it up. Typically that never happens because if a PR is high priority it probably makes nontrivial changes that warrant it being high priority, however priority can also be for "this PR is going to bitrot easily", in which case p=1 rollup=always makes sense |
Ok, sounds like rollup=always really means rollup=highly-recommended :) |
By making the proc macro abort if any symbols are out of order.
The commit also changes the proc macro collect multiple errors (of order
or duplicated symbols) and prints them at the end, which is useful if
you have multiple errors.
r? @petrochenkov