00:04
<Michael Ficarra>
or.... we just choose a different name
00:05
<Michael Ficarra>
and eventually stop trying to put new things on Array.prototype
00:05
<Michael Ficarra>
hopefully one day we can have built-in modules or something and then build out a nice stdlib
00:05
<shu>
yeah i do not think we should introduce a new MOP protocol for this
00:06
<Kris Kowal>
Symbol.facetious
00:06
<bakkot>
quite right, we should use the existing document.all protocol
00:06
<Michael Ficarra>
I was waiting for someone to bring up IsHTMLDDA
00:27
<Justin Ridgewell>
We pre-scan the source text to see if the word “group” appears anywhere, and if so, we do not install the method. Group is only accessible through computed property access were the key is not literally the string “group”.
02:16
<Jack Works>
who knows what keys they're using
maybe the engine need to record names that added to the array happens in Web
02:18
<Jack Works>
We pre-scan the source text to see if the word “group” appears anywhere, and if so, we do not install the method. Group is only accessible through computed property access were the key is not literally the string “group”.
and developers need to use it by array["gro" + "up"]() right
02:30
<shu>
maybe the engine need to record names that added to the array happens in Web
that sounds way too expensive to be feasible
02:30
<shu>
also privacy and fingerprinting concerns?
08:58
<Jack Works>
that sounds way too expensive to be feasible
I thought the engine was already doing that today, e.g. metrics of Web API usage
16:07
<shu>
those are known counters, they aren't tracking new strings
20:32
<shu>
yulia: is Nightly shipping change-array-by-copy?
20:33
<shu>
toSorted, toSpliced, and toReversed seem unlikely to be used as keys
20:33
<shu>
but i am not so sure about with
20:56
<bakkot>
with seems a lot less likely than group
21:00
<yulia>
yulia: is Nightly shipping change-array-by-copy?
only behind a build time flag
21:32
<shu>
okay, thanks
21:32
<shu>
i tried looking for the ibm issue and the other issue on the chromium issue tracker and didn't see anything
21:34
<shu>
canary population is pretty small, but i wonder if there're biases in play with people not filing issues, which would be unfortunate
21:34
<shu>
with seems a lot less likely than group
i agree, guess we'll see