Uh oh!
There was an error while loading. Please reload this page.
Rollup of 6 pull requests - #146388
Closed
GuillaumeGomez wants to merge 20 commits into
Closed
Conversation
- The empty symbol is no longer a keyword. - I don't think any of the special reserved identifiers are used for error recovery.
there is no reason this should not work, really, we're just cutting some scope for now
…rochenkov Minor symbol comment fixes. - The empty symbol is no longer a keyword. - I don't think any of the special reserved identifiers are used for error recovery. r? ``@petrochenkov``
…fee1-dead,Urgau
Strip frontmatter in fewer places
* Stop stripping frontmatter in `proc_macro::Literal::from_str` (RUST-146132)
* Stop stripping frontmatter in expr-ctxt (but not item-ctxt!) `include`s (RUST-145945)
* Stop stripping shebang (!) in `proc_macro::Literal::from_str`
* Not a breaking change because it did compare spans already to ensure there wasn't extra whitespace or comments (`Literal::from_str("#!\n0")` already yields `Err(_)` thankfully!)
* Stop stripping frontmatter+shebang inside some rustdoc code where it doesn't make any observable difference (see self review comments)
* (Stop stripping frontmatter+shebang inside internal test code)
Fixesrust-lang#145945.
Fixesrust-lang#146132.
r? fee1-dead…3, r=workingjubilee Improve C-variadic error messages: part 2 tracking issue: rust-lang#44930 a reimplementation of rust-lang#143546 that builds on rust-lang#146165. This PR - disallows coroutines (e.g. `async fn`) from having a `...` argument - disallows associated functions (both in traits and standard impl blocks) from having a `...` argument - splits up a generic "ill-formed C-variadic function" into specific errors about using an incorrect ABI, not specifying an ABI, or missing the unsafe keyword C-variadic coroutines probably don't make sense? C-variadic functions are for FFI purposes, combining that with async functions seems weird. For associated functions, we're just cutting scope. It's probably fine, but it's probably better to explicitly allow it. So for now, at least give a more targeted error message. Made to be reviewed commit-by-commit. cc ``@workingjubilee`` r? compiler
… r=fee1-dead report duplicate symbols added by the driver The panic message did not mention what symbols were duplicates, which made the panic hard to debug. This came up in [#t-compiler/help > Easiest way to find offending duplicate symbols](https://rust-lang.zulipchat.com/#narrow/channel/182449-t-compiler.2Fhelp/topic/Easiest.20way.20to.20find.20offending.20duplicate.20symbols/with/538295740). This behavior was introduced in rust-lang#138682. r? ``@fee1-dead``
…est, r=GuillaumeGomez Update `browser-ui-test` version to `0.22.2` Mostly some internal improvements and new commands (like `store-count`). r? ``@lolbinarycat``
… r=tgross35 Fix `compare_against_sw_vers` test The `saturating_sub` doesn't actually perform its intended since the version numbers are signed integers (which I changed in a later revision of rust-lang#138944). Fixes the issue described in rust-lang#138944 (comment). r? tgross35
GuillaumeGomez
commented
Sep 9, 2025
MemberAuthor
@bors r+ p=5 rollup=never |
bors
commented
Sep 9, 2025
Collaborator
bors
commented
Sep 10, 2025
Collaborator
bors added a commit
that referenced
this pull request
Sep 10, 2025
Rollup of 6 pull requests Successful merges: - #146311 (Minor symbol comment fixes.) - #146340 (Strip frontmatter in fewer places) - #146342 (Improve C-variadic error messages: part 2) - #146347 (report duplicate symbols added by the driver) - #146374 (Update `browser-ui-test` version to `0.22.2`) - #146379 (Fix `compare_against_sw_vers` test) r? `@ghost` `@rustbot` modify labels: rollup
bors
commented
Sep 10, 2025
Collaborator
💔 Test failed - checks-actions |
GuillaumeGomez
commented
Sep 10, 2025
MemberAuthor
I think CI bugged. Since another rollup is already open, let's close it. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
7 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Successful merges:
browser-ui-testversion to0.22.2#146374 (Updatebrowser-ui-testversion to0.22.2)compare_against_sw_verstest #146379 (Fixcompare_against_sw_verstest)r? @ghost
@rustbot modify labels: rollup
Create a similar rollup