-
Notifications
You must be signed in to change notification settings - Fork 13.4k
Rollup of 6 pull requests #100525
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Rollup of 6 pull requests #100525
Conversation
…ce used to create an `IntoIter` from its parts
(suggested in the review of the previous attempt to add `ArrayChunks`)
As explained in the review of the previous attempt to add `ArrayChunks`, adapters that shrink the length can't implement `TrustedLen`.
It doesn't seem to be used at all.
The "fallback" naming pre-dates introduction of `-Clink-self-contained`
Those intrinsics either panic or do nothing. They are safe.
…llot Delay a span bug if we see ty/const generic params during writeback Fixes rust-lang#99566
orphan check: rationalize our handling of constants cc `@rust-lang/types` `@rust-lang/project-const-generics` on whether you agree with this reasoning. r? types
Add `Iterator::array_chunks` (take N+1) A revival of rust-lang#92393. r? `@Mark-Simulacrum` cc `@rossmacarthur` `@scottmcm` `@the8472` I've tried to address most of the review comments on the previous attempt. The only thing I didn't address is `try_fold` implementation, I've left the "custom" one for now, not sure what exactly should it use.
Suggest removing `let` if `const let` or `let const` is used Closes rust-lang#99910
rustc_target: Update some old naming around self contained linking The "fallback" naming pre-dates introduction of `-Clink-self-contained`. Noticed when reviewing rust-lang#99500. This PR doesn't break any json target spec, but supporting per-linker-flavor startup objects needed by rust-lang#99500 will break them, so maybe next time I'll remove the compatibility names.
`assert_{inhabited,zero_valid,uninit_valid}` intrinsics are safe Those intrinsics either panic or do nothing. They are safe.
@bors r+ rollup=never p=5 |
☀️ Test successful - checks-actions |
📌 Perf builds for each rolled up PR: In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
Finished benchmarking commit (4c56655): 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. @rustbot label: -perf-regression Footnotes |
Successful merges:
Iterator::array_chunks
(take N+1) #100026 (AddIterator::array_chunks
(take N+1))let
ifconst let
orlet const
is used #100115 (Suggest removinglet
ifconst let
orlet const
is used)assert_{inhabited,zero_valid,uninit_valid}
intrinsics are safe #100487 (assert_{inhabited,zero_valid,uninit_valid}
intrinsics are safe)Failed merges:
r? @ghost
@rustbot modify labels: rollup
Create a similar rollup