-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Rollup of 10 pull requests #108096
Rollup of 10 pull requests #108096
Conversation
…atisfied diagnostics
bump up x version Refactor code
The naming of `machine` only makes sense from a mir interpreter internals perspective, but outside users talk about the `target` platform
…li-obk Migrating rustc_infer to session diagnostics (part 4) `@rustbot` label +A-translation r? rust-lang/diagnostics cc rust-lang#100717
…rister Fix unintentional UB in ui tests `@matthiaskrgr` found UB in a bunch of the ui tests. This PR fixes a batch of miscellaneous tests I didn't think needed reviewers from a particular part of the project.
…l, r=lcnr Make `InferCtxt::can_eq` and `InferCtxt::can_sub` return booleans Nobody matches on the result, nor does the result return anything useful...
make x look for x.py if shell script does not exist Fixes rust-lang#107907 Manually tested by doing the following after changes were made: 1. `cargo install --path src/tools/x` 2. checked out old version: commit hash `775c3c0` from rust-lang#99992 3. Ran `x --help` and it works. Previously, it was giving the error `x.py not found`
Use `target` instead of `machine` for mir interpreter integer handling. The naming of `machine` only makes sense from a mir interpreter internals perspective, but outside users talk about the `target` platform. As per rust-lang#108029 (comment) r? `@RalfJung`
…=compiler-errors Don't suggest `#[doc(hidden)]` trait methods with matching return type Fixes rust-lang#107983, addressing the bad suggestion. The test can probably be made more specific to this case, but I'm unsure how. `@rustbot` label +A-diagnostics
…bad-impl-trait, r=petrochenkov Better names for illegal impl trait positions Just some wording tweaks, no behavior changes.
…otriddle rustdoc: Use more let chain Got the idea after yesterday's review. r? `@notriddle`
clarify correctness of `black_box` Resolves rust-lang#107957, as described in the related issue. No code changes, just documentation.
⌛ Testing commit 5547101 with merge 508dd4ba2f0659d567ba4f8b09f31c9c8ecd7db9... |
💔 Test failed - checks-actions |
@bors retry |
☀️ Test successful - checks-actions |
📌 Perf builds for each rolled up PR: previous master: c5283576ec In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
Finished benchmarking commit (dc7a676): comparison URL. Overall result: no relevant changes - no action needed@rustbot label: -perf-regression Instruction countThis benchmark run did not return any relevant results for this metric. Max RSS (memory usage)ResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesThis benchmark run did not return any relevant results for this metric. |
The job Click to see the possible cause of the failure (guessed by this bot)
|
thanks @rust-log-analyzer, just in time 🙂 |
Successful merges:
InferCtxt::can_eq
andInferCtxt::can_sub
return booleans #108010 (MakeInferCtxt::can_eq
andInferCtxt::can_sub
return booleans)target
instead ofmachine
for mir interpreter integer handling. #108047 (Usetarget
instead ofmachine
for mir interpreter integer handling.)#[doc(hidden)]
trait methods with matching return type #108049 (Don't suggest#[doc(hidden)]
trait methods with matching return type)black_box
#108088 (clarify correctness ofblack_box
)Failed merges:
r? @ghost
@rustbot modify labels: rollup
Create a similar rollup