fix(codemode): parse canonical index keys (#37851)
This commit is contained in:
parent
8b5655ed53
commit
deee40c572
3 changed files with 64 additions and 20 deletions
|
|
@ -197,8 +197,8 @@ ultimate source of truth.
|
|||
- [x] `length`, numeric indexing, index assignment, spread, and `for...of`.
|
||||
- [x] The `thisArg` argument of `Array.from` is accepted and ignored, like JS arrows.
|
||||
- [ ] `Array.prototype.toSpliced`.
|
||||
- [ ] Canonical array/string index parsing: a key such as `"01"` must remain an ordinary property key rather than
|
||||
aliasing index `1`.
|
||||
- [x] Canonical array/string index parsing: keys such as `"01"` remain non-index properties rather than aliasing index
|
||||
`1`; arbitrary array-property assignment remains unsupported.
|
||||
- [x] `Array.prototype.sort` preserves trailing holes, while `toSorted` densifies holes into `undefined` elements,
|
||||
like JavaScript.
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue