@@ -41,7 +41,7 @@ for my ($i, $value) ($alpha->{beta}->[0]->%[ keys $alpha->{beta}->[0]->@* ]) {
41
41
42
42
This is pretty bad.
43
43
44
- With ` kv ` , we write this:
44
+ With ` indexed ` , we write this:
45
45
46
46
``` perl
47
47
for my ($i , $value ) (indexed $alpha -> {beta }-> [0]-> @*) {
@@ -66,7 +66,7 @@ just like `keys` or `values`. This is useless, and issues a warning in the new
66
66
67
67
In void context, the ` Useless use of %s in void context ` warning is issued.
68
68
69
- In list context, ` kv LIST` evalutes to a list twice the size of the array,
69
+ In list context, ` indexed LIST` evalutes to a list twice the size of the array,
70
70
meshing the values with a list of integers starting from zero. All values are
71
71
copies, unlike ` values ARRAY ` . (If your LIST was actually an array, you can
72
72
use the index to modify the array that way!)
@@ -88,9 +88,9 @@ Nothing specific predicted.
88
88
89
89
(See the examples under ** Rationale** .)
90
90
91
- I expect that docs for ` keys ` and ` values ` will be updated to reference ` kv ` as
92
- well, and we'll add a note about it to the documentation on ` for ` and possibly
93
- pair slices.
91
+ I expect that docs for ` keys ` and ` values ` will be updated to reference
92
+ ` indexed ` as well, and we'll add a note about it to the documentation on ` for `
93
+ and possibly pair slices.
94
94
95
95
When n-at-a-time foreach is no longer experimental, we should refer to the
96
96
combination of ` for my (...) (...) ` with ` indexed ` as forming an alternative to
0 commit comments