tc39/proposal-relative-indexing-method
A TC39 proposal to add an .at() method to all the basic indexable classes (Array, String, TypedArray)
HTMLMIT
Issues
- 1
- 2
Implementation status tracking
#27 opened by rkirsling - 1
- 1
TypeScript typings?
#51 opened by Semigradsky - 4
- 6
What about assignation?
#16 opened by drpicox - 17
- 1
Should it really be Math.trunc(n) || 0
#49 opened by kg - 11
Need use cases
#48 opened by jfbrennan - 3
"Fine" polyfill
#47 opened by taralx - 1
DOM collection
#46 opened by mfulton26 - 14
Add to `arguments` as well?
#14 opened by tjcrowder - 4
Assignability
#45 opened by falsandtru - 3
How about align o.at(expr) with o[expr]?
#42 opened by zeldajay - 8
[1,2,3].at('last') returns what?
#40 opened by zeldajay - 3
what the '7 more characters' are
#38 opened by fayfang - 9
How about `.get()` instead of `.at()`?
#37 opened by rauschma - 12
Stage 3 spec reviewers
#19 opened by syg - 4
can support callback also
#35 opened by nkitku - 8
How about `getItem()` and `setItem()`?
#10 opened by rauschma - 0
Array.prototype[@@unscopables]
#30 opened by rkirsling - 24
Naming proposal Array.prototype.itemAt()
#33 opened by jboler - 33
`item` on Strings has questionable value
#20 opened by michaelficarra - 1
Current plan given web incompat
#34 opened by syg - 8
- 5
Web compatibility issue with Magic360
#28 opened by evilpie - 3
Web compatibility issue with Yui2
#31 opened by evilpie - 1
What is “squooshgate”?
#24 opened by ExE-Boss - 0
Would allowing negative indices in square brackets really break existing code?
#23 opened by rauschma - 11
What if we use WebIDL algorithm for `item()` ?
#3 opened by hax - 5
Question about subclass claim in the readme
#1 opened by ljharb - 4
Polyfill is confusing
#17 opened by evilpie - 0
Please update status to Stage 2
#8 opened by leobalter - 9
- 1
Transfer to tc39-transfers
#9 opened by syg - 7
OOB behavior
#11 opened by syg - 22
- 9
What rationale using "item" instead "at"?
#2 opened by MaxGraey