Conversation
The change was "Show invisible delimiters (within comments) when pretty printing". It's useful to show these delimiters, but is a breaking change for some proc macros. Fixes rust-lang#97608.
…=Mark-Simulacrum Be a little nicer with casts when formatting `fn` pointers This removes a `fn(...) -> ...` -> `usize` -> `*const ()` -> `usize` cast. cc rust-lang#95489.
[RFC 2011] Basic compiler infrastructure Splitting rust-lang#96496 into smaller pieces as was done in rust-lang#97233. Hope review will be easier. This PR practically contains no logic and only serves as a building ground for the actual code that will be placed in a posterior step. * Adds `context.rs` to place the new `assert!` logic. Has a lot of unused elements but all of them are used by the implementation. * Creates an unstable flag because the feature is not yet complete and also to allow external feedback. * Creates the necessary `sym` identifiers that are mostly based on the library elements -> https://github.com/rust-lang/rust/blob/master/library/core/src/asserting.rs * Modifies `assert.rs` to branch to `context.rs` if the unstable flag is enabled. * Adds a test to satisfy tidy but the test does nothing in reality.
…ftSpider Fix JSON reexport ICE Fixes rust-lang#97432. The problem was that the ID was conflicting because the reexports have the same one. To fix it, I "extended" it by adding the `Symbol` into it as well. r? `@notriddle`
…exports, r=Nemo157 Rustdoc anonymous reexports Fixes rust-lang#97615. r? `@Nemo157`
Revert rust-lang#96682. The change was "Show invisible delimiters (within comments) when pretty printing". It's useful to show these delimiters, but is a breaking change for some proc macros. Fixes rust-lang#97608. r? ``@petrochenkov``
|
@bors r+ rollup=never p=5 |
|
📌 Commit 1d71237 has been approved by |
|
☀️ Test successful - checks-actions |
|
Finished benchmarking commit (44e9516): comparison url. Instruction count
Max RSS (memory usage)Results
CyclesResults
If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. Next Steps: If you can justify the regressions found in this perf run, please indicate this with @rustbot label: +perf-regression Footnotes |
|
The improvements outweigh the regressions (which are pretty small and contained in secondary benchmarks). Given it's in a rollup, it's not worth the effort to investigate. @rustbot label: +perf-regression-triaged |
Successful merges:
fnpointers #97420 (Be a little nicer with casts when formattingfnpointers)Failed merges:
r? @ghost
@rustbot modify labels: rollup
Create a similar rollup