-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Rollup of 6 pull requests #110736
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 6 pull requests #110736
Conversation
This code was added in 9dc5dfb and 704050d because the browser- native checkbox was `display: none`, breaking native keyboard accessibility. The native checkbox is now merely `appearance: none`, which does not turn off [behavior semantics], so JavaScript to reimplement it isn't needed any more. [behavior semantics]: https://w3c.github.io/csswg-drafts/css-ui/#appearance-semantics
This code was added back when `border-color: currentColor` was used. Since it was changed in ad9a89e, the current color is not used any more.
…ndlekey, r=GuillaumeGomez rustdoc: clean up settings.css and settings.js `handleKey` was added in 9dc5dfb and 704050d because the browser-native checkbox was `display: none`, breaking native keyboard accessibility. The native checkbox is now merely `appearance: none`, which does not turn off [behavior semantics], so JavaScript to reimplement it isn't needed any more. [behavior semantics]: https://w3c.github.io/csswg-drafts/css-ui/#appearance-semantics The other, one line change to settings.css is follow-up to rust-lang#110205
…=cuviper Add note about change in bootstrap defaults Not a huge fan of the proposed wording, open to changes in that. Per rust-lang#106886 (comment). cc `@jonhoo` r? `@cuviper` perhaps?
…t, r=jyn514 stop `x fmt` formatting untracked directories I don't think there's anything else to do? I've confirmed that you get a "skip untracked path foo/ during rustfmt invocations" for the alternative build directory. r? `@jyn514`
Fix printing native CPU on cross-compiled compiler. If `rustc` is cross-compiled from a different host, then the "native" entry in `rustc --print=target-cpus` would not appear. There is a check in the printing code that will avoid printing the "native" entry if the user has passed `--target`. However, that check was comparing the `--target` value with the `LLVM_TARGET_TRIPLE` which is the triple of the host that `rustc` was built on (the "build" target in Rust lingo), not the target it was being built for (the "host" in Rust lingo). This fixes it to use the target that LLVM was built for (which I'm pretty sure this is the correct function to determine that). This fixes the cpu listing for aarch64-apple-darwin which is built on CI using the x86_64-apple-darwin host.
Fix grammar in core::hint::unreachable_unchecked() docs Fixes a minor grammar error in the docs for core::hint::unreachable_unchecked()
Don't infer fn return type to return itself Fixes rust-lang#110687
@bors r+ rollup=never p=6 |
☀️ Test successful - checks-actions |
📌 Perf builds for each rolled up PR: previous master: 7f94b314ce In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
Finished benchmarking commit (8991768): 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.
CyclesResultsThis 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.
|
Successful merges:
x fmt
formatting untracked directories #110664 (stopx fmt
formatting untracked directories)Failed merges:
r? @ghost
@rustbot modify labels: rollup
Create a similar rollup