Rollup of 7 pull requests#128501
Closed
matthiaskrgr wants to merge 22 commits intorust-lang:masterfrom
Closed
Conversation
This silences this rust-analyzer-specific error: `expected !, found ()` Signed-off-by: Martin Kröning <martin.kroening@eonerc.rwth-aachen.de>
Signed-off-by: Martin Kröning <martin.kroening@eonerc.rwth-aachen.de>
…` and aren't accidentally usable on completely unrelated HIR nodes
Signed-off-by: Martin Kröning <martin.kroening@eonerc.rwth-aachen.de>
Signed-off-by: Martin Kröning <martin.kroening@eonerc.rwth-aachen.de>
Signed-off-by: Martin Kröning <martin.kroening@eonerc.rwth-aachen.de>
…unknown-linux-target-page, r=pietroalbini Add target page for riscv64gc-unknown-linux-gnu I was reading rust-lang#113739 and realized I knew most of the information necessary to create the `riscv64gc-unknown-linux-gnu` target page.
…fe_fn, r=joboet fix(hermit): `deny(unsafe_op_in_unsafe_fn)` Tracking issue: rust-lang#127747 r? workingjubilee CC: `@stlankes`
Assert that all attributes are actually checked via `CheckAttrVisitor` and aren't accidentally usable on completely unrelated HIR nodes based on rust-lang#128402 After this PR, adding a new attribute will ICE on any use of that attribute unless it gets a handler added.
interpret: on a signed deref check, mention the right pointer in the error When a negative offset (like `ptr.offset(-10)`) goes out-of-bounds, we currently show an error saying that we expect the *resulting* pointer to be inbounds for 10 bytes. That's confusing, so this PR makes it so that instead we say that we expect the *original* pointer `ptr` to have 10 bytes *to the left*. I also realized I can simplify the pointer arithmetic logic and handling of "staying inbounds of a target `usize`" quite a bit; the second commit does that.
…compiler-errors Fix removed `box_syntax` diagnostic if source isn't available Fix rust-lang#128442
fix dropck documentation for `[T;0]` special-case fixes rust-lang#110288. r? `@lcnr`
…ing, r=tgross35 chore: refactor backtrace formatting Replace `write_str()` with the `writeln!()` macro, consolidating multiple write operations.
Member
Author
|
@bors r+ rollup=never p=7 |
Collaborator
Collaborator
|
The job Click to see the possible cause of the failure (guessed by this bot) |
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 free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
11 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:
deny(unsafe_op_in_unsafe_fn)#128433 (fix(hermit):deny(unsafe_op_in_unsafe_fn))CheckAttrVisitorand aren't accidentally usable on completely unrelated HIR nodes #128444 (Assert that all attributes are actually checked viaCheckAttrVisitorand aren't accidentally usable on completely unrelated HIR nodes)box_syntaxdiagnostic if source isn't available #128496 (Fix removedbox_syntaxdiagnostic if source isn't available)[T;0]special-case #128497 (fix dropck documentation for[T;0]special-case)r? @ghost
@rustbot modify labels: rollup
Create a similar rollup