-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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 5 pull requests #124849
Rollup of 5 pull requests #124849
Conversation
This change constructs the search form HTML using JavaScript, instead of plain HTML. It uses a custom element because - the [parser]'s insert algorithm runs the connected callback synchronously, so we won't get layout jank - it requires very little HTML, so it's a real win in size [parser]: https://html.spec.whatwg.org/multipage/parsing.html#create-an-element-for-the-token This shrinks the standard library by about 60MiB, by my test.
…, r=GuillaumeGomez rustdoc: dedup search form HTML This change constructs the search form HTML using JavaScript, instead of plain HTML. It uses a custom element because - the [parser]'s insert algorithm runs the connected callback synchronously, so we won't get layout jank - it requires very little HTML, so it's a real win in size [parser]: https://html.spec.whatwg.org/multipage/parsing.html#create-an-element-for-the-token This shrinks the standard library by about 60MiB, by my test. There should be no visible changes. Just use less disk space.
…iler-errors generalize hr alias: avoid unconstrainable infer vars fixes rust-lang/trait-system-refactor-initiative#108 see inline comments for more details r? `@compiler-errors` cc `@BoxyUwU`
…ease narrow down visibilities in `rustc_parse::lexer` Found something visibility can be narrowed down on `rustc_parse::lexer`. The mods only used in lexer, so it is ok to limit visibility to `pub(super)`, see https://github.com/rust-lang/rust/blob/master/compiler/rustc_parse/src/lexer/mod.rs#L22-L25
…rrors replace another Option<Span> by DUMMY_SP This was missed in rust-lang#122480.
Don't ICE when we cannot eval a const to a valtree in the new solver Use `const_eval_resolve` instead of `try_const_eval_resolve` because naming aside, the former doesn't ICE when a value can't be evaluated to a valtree. r? lcnr
@bors r+ rollup=never p=5 |
☀️ Test successful - checks-actions |
📌 Perf builds for each rolled up PR:
previous master: 0f40f14b61 In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
Finished benchmarking commit (b923ea4): comparison URL. Overall result: ✅ improvements - no action needed@rustbot label: -perf-regression Instruction countThis is a highly reliable metric that was used to determine the overall result at the top of this comment.
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. Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 676.385s -> 675.093s (-0.19%) |
Successful merges:
rustc_parse::lexer
#124832 (narrow down visibilities inrustc_parse::lexer
)r? @ghost
@rustbot modify labels: rollup
Create a similar rollup