Sender | Message | Time |
---|---|---|
11 Oct 2024 | ||
Aki | Do we keep a list of what we consider a stage 4-eligible implementation? | 02:31:58 |
rkirsling | > shipping implementations, such as that provided by two independent VMs I feel like this is one of those "has a very concrete meaning in practice and needs to be kept abstract on paper" things | 02:35:12 |
rkirsling | (also why tf does Element for Android not all typing formatted text) | 02:37:29 |
rkirsling | * (also why tf does Element for Android not allow typing formatted text) | 02:37:38 |
Aki | So in practice, JSC, SpiderMonkey, or V8 and that's that? | 02:39:07 |
rkirsling | in theory others like XS should count but the shipping experience as "proof that the web didn't break" is so important | 02:42:48 |
ljharb | they do count when web compat isn’t a concern | 06:30:16 |
ljharb | i have an open PR on the process doc that suggests we should define “risk areas” for each proposal, and use those to inform what counts - ie, what reassurances are most needed | 06:31:10 |
nicolo-ribaudo | Process proposal to make a proposal's title blink it it changes Array.prototype | 06:33:04 |
nicolo-ribaudo | * Process proposal to make a proposal's title blink if it changes Array.prototype | 06:33:11 |
nicolo-ribaudo |
My use case is that I need an immutable weakset. For | 09:01:28 |
nicolo-ribaudo | *
My use case is that I need an immutable weakset. For | 09:01:47 |
nicolo-ribaudo | My
| 09:02:28 |
nicolo-ribaudo | * My
| 09:04:10 |
ljharb | how would the values be "cloned"? or would it just put the same === items in both WMs/WSs? | 09:18:41 |
nicolo-ribaudo | Yes | 09:19:02 |
nicolo-ribaudo | It's like doing `new Set(oldSet)`, except that you cannot do this with WeakSets because they are not iterable | 09:19:49 |
nicolo-ribaudo | * Yes, same items | 09:19:59 |
nicolo-ribaudo | * It's like doing new Set(oldSet) , except that you cannot do this with WeakSets because they are not iterable | 09:20:48 |
nicolo-ribaudo | And this would be much easier to implement in engines than in userland, because engines can iterate over WeakSet contents | 09:21:38 |
Justin Ridgewell | Why not build a wrapper over a WeakSet that prevents writes? | 09:31:56 |
nicolo-ribaudo | I trust my code to not mutate the WeakSet , so I don't need to prevent writes | 09:32:56 |
nicolo-ribaudo | I need to keep around both the old one and the new one | 09:33:47 |
nicolo-ribaudo | Oh, I found https://github.com/tc39/proposal-readonly-collections/issues/2. WeakSet.prototype.diverge() is exactly what I need | 09:36:47 |
Richard Gibson | not all implementations can iterate over WeakSet contents; XS in particular uses an inverted approach that would not support this | 12:18:34 |
yulia | Download ima_fac0ac5.jpeg | 12:20:51 |
yulia | Tg5 workshop photo | 12:20:55 |
12 Oct 2024 | ||
ljharb | Temporal change incoming? https://twitter.com/potetotes/status/1844422986574799037 | 01:14:33 |
shu | if california eminent domains the moon we can just use pacific time | 07:00:32 |
Andreu Botella (at TC39, 🕐 JST) | The Sea of Tranquility truly is the Moon's Pacific Ocean | 07:06:57 |