| 01:07 | <sideshowbarker> | cyber_dodo: You may want to read up on the previous W3C PICS and POWDER proposals, and the rest of the history around this idea — which goes back 30 years. The summary is that it’s all been tried before, and it’s always failed to get adoption — for reasons that are fairly well understood. So you might end up find it’s not a great use of your time to end up re-proposing it somewhere. |
| 01:45 | <Dex Prime> | This may be a strange question, but what is this group about? I'm new to Matrix and don't really know what it is lol |
| 01:46 | <sideshowbarker> | https://whatwg.org/faq |
| 01:46 | <Dex Prime> | Thank you! |
| 22:19 | <akaster> | Is there a meaningful difference between an optional any argument being missing vs being the value undefined? https://github.com/WebAssembly/spec/issues/1861 |
| 22:20 | <akaster> | If I make WebAssembly.Global's constructor check how many arguments are in the VM, I fail 3 tests. But If I just treat missing as undefined, it agrees with the other three engines 🤔 |
| 22:25 | <Meghan Denny> | i interpreted the difference as being foo() vs foo(undefined) |
| 22:26 | <Meghan Denny> | although it'd be unobservable inside the body unless perhaps through like arguments.length |
| 22:32 | <akaster> | right.. in this case, everyone is treating new WebAssembly.Global({ value: "f64" }) the same as new WebAssembly.Global({ value: "f64", undefined) |
| 22:32 | <akaster> | which... might not be something that author code can detect, but I can determine the difference in the implementation by inspecting private state of the JS engine |