about summary refs log tree commit diff
path: root/tests/rustdoc-js-std/string-from_ut.js
diff options
context:
space:
mode:
authorChris Denton <chris@chrisdenton.dev>2025-04-19 19:30:47 +0000
committerGitHub <noreply@github.com>2025-04-19 19:30:47 +0000
commit92adbd323aa99c78341555ffcdbbffd009e1611d (patch)
tree75f2e1ed984ab1ba7349bb4e634e0e6bb26baa16 /tests/rustdoc-js-std/string-from_ut.js
parent5d2375f789e88d0ac6dbbd828082559a5d2fa8c6 (diff)
parentf121c7c3605d195a05a9802735994e3576be9d62 (diff)
downloadrust-92adbd323aa99c78341555ffcdbbffd009e1611d.tar.gz
rust-92adbd323aa99c78341555ffcdbbffd009e1611d.zip
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?
Diffstat (limited to 'tests/rustdoc-js-std/string-from_ut.js')
0 files changed, 0 insertions, 0 deletions