Chris Denton 92adbd323a

Rollup merge of #139533 - jogru0:130711, r=Mark-Simulacrum ...

add next_index to Enumerate

Proposal: https://github.com/rust-lang/libs-team/issues/435
Tracking Issue: #130711

This basically just reopens #130682 but squashed and with the new function and the feature gate renamed to `next_index.`

There are two questions I have already:
- Shouldn't we add test coverage for that? I'm happy to provide some, but I might need a pointer to where these test would be.
  - Maybe I could actually also add a doctest?
- For now, I just renamed the feature name in the unstable attribute to `next_index`, as well, so it matches the new name of the function. Is that okay? And can I just do that and use any string, or is there a sealed list of features defined somewhere where I also need to change the name?

2025-04-19 19:30:47 +00:00

..

async_iter

…

ffi

…

fmt

…

hash

…

io

…

iter

…

net

…

num

…

ops

…

panic

…

alloc.rs

…

any.rs

…

array.rs

…

ascii_char.rs

…

ascii.rs

…

asserting.rs

…

atomic.rs

…

bool.rs

…

bstr.rs

…

cell.rs

…

char.rs

…

clone.rs

…

cmp.rs

…

const_ptr.rs

…

convert.rs

…

error.rs

…

ffi.rs

…

future.rs

…

hint.rs

…

intrinsics.rs

…

lazy.rs

…

lib.rs

…

macros.rs

…

manually_drop.rs

…

mem.rs

…

nonzero.rs

…

ops.rs

…

option.rs

…

panic.rs

…

pattern.rs

…

pin_macro.rs

…

pin.rs

…

ptr.rs

…

result.rs

…

simd.rs

…

slice.rs

…

str_lossy.rs

…

str.rs

…

task.rs

…

time.rs

…

tuple.rs

…

unicode.rs

…

waker.rs

…