-
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 7 pull requests #92352
Rollup of 7 pull requests #92352
Conversation
Fixes rust-lang#92073 There's not really anything we can do with them, and they're causing ICEs. I'm not using a wildcard match, as we should check that any new `PredicateKind`s are handled properly by rustdoc.
…, r=cjgillot Ignore other `PredicateKind`s in rustdoc auto trait finder Fixes rust-lang#92073 There's not really anything we can do with them, and they're causing ICEs. I'm not using a wildcard match, as we should check that any new `PredicateKind`s are handled properly by rustdoc.
Remove VCVARS_BAT This environment variable is no longer used. It was used in the original Azure Pipelines configuration (rust-lang#60777). When GitHub Actions were added (rust-lang#70190), it was no longer used, and I suspect it was just an oversight while transitioning the configuration.
…acrum Add a test suite for stringify macro This attempts to cover the behavior of `stringify!` on various interpolated syntax tree nodes. The pretty printer has a history of unsightly whitespace (double spaces, missing spaces, spaces where there shouldn't be spaces) — rust-lang#91437, rust-lang#91562, rust-lang#91568. There are several such issues left; the test cases that I consider to be currently behaving incorrectly are marked with `// FIXME` in the PR.
Add myself to .mailmap
…ns, r=cjgillot Tighten span when suggesting lifetime on path This is kind of a hack. Really the issue here is that we want to suggest the segment's span if the path resolves to something defined outside of the macro, and the macro's span if it resolves to something defined within.. I'll look into seeing if we can do something like that. Fixes rust-lang#92324 r? `@cjgillot`
…r=Manishearth Document units for `std::column` Fixes rust-lang#92301. r? ``@Manishearth`` (for the terminology and the Chinese)
…=lnicola ⬆️ rust-analyzer r? ``@ghost``
@bors r+ rollup=never p=7 |
📌 Commit 11c71d2 has been approved by |
⌛ Testing commit 11c71d2 with merge c82eff091b454cb2618a685a56d507fc3ab32f64... |
💔 Test failed - checks-actions |
The job Click to see the possible cause of the failure (guessed by this bot)
|
@bors retry crates.io timeout
|
@bors r+ |
💡 This pull request was already approved, no need to approve it again.
|
📌 Commit 11c71d2 has been approved by |
☀️ Test successful - checks-actions |
Finished benchmarking commit (83b15bf): comparison url. Summary: This benchmark run did not return any relevant changes. If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. @rustbot label: -perf-regression |
Successful merges:
PredicateKind
s in rustdoc auto trait finder #92076 (Ignore otherPredicateKind
s in rustdoc auto trait finder)std::column
#92335 (Document units forstd::column
)Failed merges:
r? @ghost
@rustbot modify labels: rollup
Create a similar rollup