Conversation
Tweaked `try_collect()` to accept more `Try` types Updated feature attribute for tracking issue
Signed-off-by: Alex Saveau <saveau.alexandre@gmail.com>
I have found this code confusing for years. I've always roughly understood it, but never exactly. I just made my fourth(?) attempt and finally cracked it. This commit improves the comments. In particular, it explicitly describes how you can't do a custom fold/visit of any type; there are actually a handful of "types of interest" (e.g. `Ty`, `Predicate`, `Region`, `Const`) that can be custom folded/visted, and all other types just get a generic traversal. I think this was the part that eluded me on all my prior attempts at understanding. The commit also updates comments to account for some newer changes such as the fallible/infallible folding distinction, does some minor reorderings, and moves one `impl` to a better place.
It seems to be unused and it is incorrect for arm/aarch64 anyway.
Update tracking issue numbers for inline assembly sub-features The main tracking issue for inline assembly is [closed](rust-lang#72016 (comment)), further tracking of the remaining sub-features has been moved to separate tracking issues.
…s, r=BoxyUwU Improve comments about type folding/visiting. I have found this code confusing for years. I've always roughly understood it, but never exactly. I just made my fourth(?) attempt and finally cracked it. This commit improves the comments. In particular, it explicitly describes how you can't do a custom fold/visit of any type; there are actually a handful of "types of interest" (e.g. `Ty`, `Predicate`, `Region`, `Const`) that can be custom folded/visted, and all other types just get a generic traversal. I think this was the part that eluded me on all my prior attempts at understanding. The commit also updates comments to account for some newer changes such as the fallible/infallible folding distinction, does some minor reorderings, and moves one `impl` to a better place. r? `@BoxyUwU`
…jsha Generate list instead of div items in sidebar Fixes rust-lang#92986. Surprisingly, we didn't have much CSS for this... [Demo](https://rustdoc.crud.net/imperio/links-in-sidebar/std/index.html). r? `@jsha`
Add MAIN_SEPARATOR_STR
Currently, if someone needs access to the path separator as a str, they need to go through this mess:
```rust
unsafe {
std::str::from_utf8_unchecked(slice::from_ref(&(MAIN_SEPARATOR as u8)))
}
```
This PR just re-exports an existing path separator str API.
Even more let_else adoptions Continuation of rust-lang#89933, rust-lang#91018, rust-lang#91481, rust-lang#93046, rust-lang#93590.
Add a `try_collect()` helper method to `Iterator` Implement `Iterator::try_collect()` as a helper around `Iterator::collect()` as discussed [here](https://internals.rust-lang.org/t/idea-fallible-iterator-mapping-with-try-map/15715/5?u=a.lafrance). First time contributor so definitely open to any feedback about my implementation! Specifically wondering if I should open a tracking issue for the unstable feature I introduced. As the main participant in the internals discussion: r? `@scottmcm`
Fix ICE when using Box<T, A> with pointer sized A Fixes rust-lang#78459 Note that using `Box<T, A>` with a more than pointer sized `A` or using a pointer sized `A` with a Box of a DST will produce a different ICE (rust-lang#92054) which is not fixed by this PR.
…Simulacrum Remove CFG_PLATFORM It seems to be unused and it is incorrect for arm/aarch64 anyway.
…p_fix, r=Manishearth Clippy: Don't lint `needless_borrow` in method receiver positions r? `@Manishearth` cc `@camsteffen` `@Jarcho` cc rust-lang/rust-clippy#8441 Let's get this fix in before the beta branching tomorrow.
|
@bors r+ rollup=never p=9 |
|
📌 Commit 39c1748 has been approved by |
|
☀️ Test successful - checks-actions |
|
Finished benchmarking commit (73a7423): comparison url. Summary: This benchmark run shows 13 relevant regressions 😿 to instruction counts.
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 |
|
@matthiaskrgr none of the rolled up PRs here seem remotely suspicious as to why there would be a performance regression. Any ideas? |
|
Yeah, the only thing that looks like it might have a very very slight performance impact is the ICE-fix but maybe it is just unlucky noise..? |
Successful merges:
try_collect()helper method toIterator#94041 (Add atry_collect()helper method toIterator)needless_borrowin method receiver positions #94085 (Clippy: Don't lintneedless_borrowin method receiver positions)Failed merges:
r? @ghost
@rustbot modify labels: rollup
Create a similar rollup