-
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
Rollup of 10 pull requests #107161
Rollup of 10 pull requests #107161
Conversation
No functional changes intended. The LLVM commit llvm/llvm-project@e6b0221 added `TargetExtTyID` to the `TypeID` enum. This adapts `RustWrapper` accordingly.
It was disabled in rust-lang#75103 due to an LLVM bug, but followup comments have confirmed that it builds fine on Fedora with LLVM 15.
llvm-wrapper: adapt for LLVM API change No functional changes intended. The LLVM commit llvm/llvm-project@e6b0221 added `TargetExtTyID` to the `TypeID` enum. This adapts `RustWrapper` accordingly.
Improve the documentation of `black_box` There don't seem to be many great resources on how `black_box` should be used, so I added some information here
…losure, r=TaKO8Ki Label closure captures/generator locals that make opaque types recursive cc rust-lang#46415 (comment)
Fix `SingleUseLifetime` ICE Fixes rust-lang#104440 cc: `@matthiaskrgr`
Re-enable building rust-analyzer on riscv64 It was disabled in rust-lang#75103 due to an LLVM bug, but followup comments have confirmed that it builds fine on Fedora with LLVM 15. r? `@Mark-Simulacrum` cc `@matklad` `@davidlt`
…ulacrum Add new bootstrap members to triagebot.toml `@ozkanonur` if you want to be assigned to review PRs too, just post a message to this thread. Should a `T-bootstrap` label be created, since `src/tools/tidy` is assigned to the `bootstrap` members, but labeled `A-testsuite` (and not `A-bootstrap`) ? cc `@jyn514`
…i-obk Custom MIR: Support binary and unary operations Lower binary and unary operations directly to corresponding unchecked MIR operations. Ultimately this might not be syntax we want, but it allows for experimentation in the meantime. r? ```@oli-obk``` ```@JakobDegen```
…didats-4, r=lcnr Implement some more predicates in the new solver Implement a few more goals. The subtype goal specifically is important, since it's required for this code to compile: ``` fn main() { let mut x = vec![]; x.push(1i32); } ``` (I think we emit a subtype goal here because of coercion). Drive-by: Also implements `--compare-mode=next-solver` -- I've been using this locally a lot to find out what works and what doesn't. I'm also happy to split this out into another PR. r? `@lcnr`
…n, r=m-ou-se Add note about absolute paths to Path::join The note already exists on `PathBuf::push`, but I think it is good to have it on `Path::join` as well since it can cause issues if you are not careful with your input.
… r=notriddle Migrate scraped-examples top and bottom "borders" to CSS variables r? `@notriddle`
@bors r+ rollup=never p=10 |
⌛ Testing commit 6a040d7 with merge 52887c9a95969d8d2ccc0cedcdead509ac28e413... |
💔 Test failed - checks-actions |
The job Click to see the possible cause of the failure (guessed by this bot)
|
Hmm thats weird, none of the PRs looks related at first glance, but the error also don't really look like they might be spurious..? |
Oh well, I just made two more (disjoint) rollups. If one of those fails, then I guess we'll have a better idea of which one is the cause for the bors failure 😅 |
Successful merges:
black_box
#106144 (Improve the documentation ofblack_box
)SingleUseLifetime
ICE #106935 (FixSingleUseLifetime
ICE)Failed merges:
r? @ghost
@rustbot modify labels: rollup
Create a similar rollup