| 01:01 | <domfarolino> | Seems infra does not describe an "array"; so what is our idiomatic of removing a single element in an array in spec prose. Do we pop? Do we "remove the last-inserted element"? If I can guarantee there is only one element, can I "empty" it? |
| 08:05 | <annevk> | littledan: is https://github.com/WebAssembly/threads build on top of JavaScript's model or actual threads? |
| 08:06 | <annevk> | domfarolino: are we talking about a list or an actual JavaScript object? |
| 08:07 | <littledan> | I think it's supposed to kind of correspond to JS's model, but in WebAssembly's core specification, they would like to avoid referencing JS or web specs, to ensure it works for other environments as well |
| 08:07 | <littledan> | Correspondingly, JS doesn't layer on top of Wasm either ... |
| 08:09 | <littledan> | A long-term hope among many who work on Wasm is to create a shared, GC'd heap, even if that's not suitable for JS |
| 08:09 | <annevk> | littledan: as I understood it from Luke, Wasm Threads effectively use workers and postMessage() under the hood, so yeah, they'd be affected in the sense that this is how they'd end up working |
| 08:09 | <annevk> | littledan: right, okay, so these Wasm Threads are the worker things then |
| 08:09 | <littledan> | Right... The idea is to encode this correspondence in the JS and Web APIs |
| 08:09 | <annevk> | littledan: then yeah, feel free to also post there or move it? |
| 08:09 | <annevk> | littledan: I keep wondering when we'll do host integration for Wasm btw |
| 08:09 | <annevk> | littledan: do you know anything about that? |
| 08:09 | <littledan> | What's missing? |
| 08:10 | <annevk> | littledan: shouldn't module fetching branch on the Wasm MIME type somehow? |
| 08:10 | <littledan> | I mean, I should know, since I'm the editor of the host integration spec |
| 08:10 | <annevk> | littledan: or can you not import Wasm from JS? |
| 08:10 | <littledan> | Well, it does, in the web spec |
| 08:10 | <annevk> | littledan: but module fetching is defined in HTML |
| 08:10 | <littledan> | I hope to make more progress on the module integration this week |
| 08:11 | <littledan> | We should have a PR against HTML for proper layering, I agree |
| 08:11 | <littledan> | Some of the HTML modules refactoring will be in common |
| 08:11 | <annevk> | littledan: okay, I'm wondering about the HTML bits in particular |
| 08:11 | <annevk> | littledan: HTML also has a bunch of JavaScript integration stuff, hopefully less of that is needed for Wasm since it only does modules, but it seems at least some would be needed |
| 08:12 | <littledan> | https://github.com/WebAssembly/esm-integration/pull/21 |
| 08:13 | <littledan> | Specifically https://littledan.github.io/esm-integration/#html-modifications |
| 08:14 | <littledan> | We discussed this at TPAC and folks there seemed onboard, but I have had trouble convincing people in the tooling ecosystem |
| 08:14 | <littledan> | So I wanted to improve docs and talk more with them first |
| 08:15 | <littledan> | But if you are interested in an HTML PR, I am happy to do that |
| 08:15 | <annevk> | littledan: ah great |
| 08:16 | <annevk> | littledan: so I like that kind of thing, as it makes extensions more visible |
| 08:17 | <littledan> | OK, good to know |
| 08:17 | <annevk> | littledan: it also paves the path for adding other types, such as JSON |
| 08:18 | <littledan> | JSON would be nice and easy! |
| 08:18 | <littledan> | Everyone loves JSON |
| 08:18 | <annevk> | 😃 |
| 08:19 | <littledan> | So what module types do we want to support soon? JS, Wasm, HTML, CSS, JSON, any more? |
| 08:19 | <littledan> | CSV :) |
| 08:19 | <littledan> | CBOR? Spec people love CBOR |
| 08:21 | <littledan> | Re: we could allow importing images and videos, to be abstract assets, to be put in src |
| 08:22 | <littledan> | Re: asset imports https://github.com/sebmarkbage/ecmascript-asset-references |
| 08:26 | <littledan> | annevk: ^ |
| 08:27 | <annevk> | littledan: a lot of those are discussed in various issues |
| 08:27 | <annevk> | littledan: I'm assuming CBOR is trolling |
| 08:27 | <annevk> | littledan: and I'm not sure CSV has a good enough parser specification |
| 08:27 | <littledan> | Yeah, half |
| 08:28 | <littledan> | If I said YAML it'd be trolling |
| 08:28 | <annevk> | I guess if the packaging thing ends up happening there might really be CBOR |
| 08:28 | <littledan> | OK, I will check issues |
| 08:28 | <annevk> | littledan: https://github.com/w3c/webcomponents/issues/759 |
| 08:28 | <annevk> | littledan: https://github.com/whatwg/html/issues/4315 |
| 08:29 | <annevk> | littledan: w3c/webcomponents also has a JSON issue and various HTML issues |
| 08:29 | <littledan> | Oh thanks, I missed the JSON issue |
| 08:29 | <annevk> | littledan: haven't seen anything for CSV, but it did cross my mind |
| 08:29 | <littledan> | I have seen another custom JS module system that exposes JSON modules |
| 10:15 | <domfarolino> | Talking about a list, i.e., whatever we have “Let x be an array” |
| 10:21 | <Ms2ger> | ? |
| 10:22 | <Ms2ger> | domfarolino, avoid saying that, I suppose? Infra defines lists, not arrays: https://infra.spec.whatwg.org/#lists |
| 10:43 | <annevk> | Yeah, please don't use the word array for something that's a list |
| 10:44 | <annevk> | (Note that IDL will eventually be such that it converts a list into an array depending on what the getter/method does.) |
| 10:45 | <annevk> | s/does/returns/ |
| 16:06 | <annevk> | Domenic: left a comment on the PR for the worklet event loop issue; I still don't see it working as the tasks aren't really associated with anything and elsewhere we blindly copy particular state of a task if it's in a window event loop |
| 17:29 | <domfarolino> | annevk: For context, was mostly referring to step 2 in https://html.spec.whatwg.org/multipage/images.html#updating-the-source-set, as I'm refactoring it a bit |
| 17:30 | <domfarolino> | Not sure if I should keep it as "array", or "list". |
| 17:30 | <annevk> | domfarolino: changing that to https://infra.spec.whatwg.org/#lists would be great |
| 17:30 | <domfarolino> | ok |
| 17:30 | <annevk> | domfarolino: a lot in HTML predates Infra |
| 17:30 | <domfarolino> | I figured haha |
| 17:30 | <annevk> | domfarolino: before Infra everyone made up data structures as they went |
| 17:31 | <annevk> | domfarolino: without defining them... |
| 17:31 | <domfarolino> | perfect :( |
| 17:31 | <domfarolino> | Yeah Infra i really nice |
| 17:31 | <domfarolino> | is* |