| 12:24 | <ondras> | URLSearchParams::forEach |
| 12:24 | <ondras> | please, where is this specced? |
| 12:42 | <Ms2ger> | ondras, probably https://heycam.github.io/webidl/#es-forEach |
| 12:43 | <ondras> | Ms2ger: a-ha! I looked at the URLSearchParams specifically and there was no sign of forEach :/ |
| 12:44 | <Ms2ger> | But there was! Only it was spelled "iterable<USVString, USVString>;" :) |
| 12:45 | <ondras> | :D |
| 12:46 | <ondras> | yeah, the "iterable" looked more like "haz @@iterator" |
| 12:48 | <Ms2ger> | And of course it *also* means that! |
| 12:48 | Ms2ger | returns to cursing RelativeTimeFormat |
| 12:49 | <ondras> | :P |
| 17:57 | <TabAtkins> | Domenic: Yo, which is the canonical definition of ReadableStream, Fetch or Streams? They're both claiming to define the term right now. |
| 18:09 | <TimothyGu> | TabAtkins: Domenic's traveling, but it's Streams |
| 18:09 | <TimothyGu> | I think there's an issue open somewhere for removing one of the definitions |
| 18:09 | <TabAtkins> | Doesn't look like it, but I'm opening one right now anyway. |
| 18:09 | <TimothyGu> | https://github.com/whatwg/streams/issues/861 |
| 18:09 | <TimothyGu> | https://github.com/heycam/webidl/issues/445 |
| 18:09 | <TimothyGu> | https://github.com/whatwg/streams/issues/372 |
| 18:09 | <TabAtkins> | Ah, that didn't come up when I searched. |
| 18:12 | <TabAtkins> | All right, I went ahead and filed my issue anyway, as I can provide an actual suggestion for a fix that doesn't disrupt the current spec. |
| 18:12 | <Domenic> | One way of looking at the issue is that Bikeshed's overload of "interface" to mean both "JS class" and "Web IDL type" is causing problems, because internally Streams wants to refer to its JS class definition, whereas most other specs want to refer to Fetch's Web IDL type definition. |
| 18:13 | <TabAtkins> | ...what's the purpose for distinguishing the two? |
| 18:15 | <Domenic> | Well, JS classes are defined using JS semantics, then you define a Web IDL type to wrap them. A bit like Array vs. sequence<>, or Object vs. object. |
| 18:15 | <TabAtkins> | Yes, they're definitely distinct things, but what's the *purpose* in distinguishing them in a spec? |
| 18:16 | <Domenic> | Specs that don't use Web IDL, like Streams itself, appreciate the distinction? |
| 18:16 | <Domenic> | Whereas specs that do, are a bit ill-founded if they don't refer to a proper Web IDL type |
| 18:16 | <Domenic> | It's not a great system |
| 18:16 | <Domenic> | (Streams, I mean, not Bikeshed's) |
| 18:19 | <TabAtkins> | I don't understand why Streams isn't defining the IDL type too, tho; the rest of the ecosystem needs IDL to work on. |
| 18:23 | <TabAtkins> | (This is relevant to me because I'm currently defining the CSS Parser API to be able to take in a ReadableStream as input: http://wicg.github.io/CSS-Parser-API/#typedefdef-cssstringsource) |
| 20:21 | <jyasskin> | TabAtkins: If you're trying to use those streams from an `in parallel` context, check out the very in-progress "Stream algorithms" section in https://github.com/jyasskin/webpackage/blob/loading-spec/loading.bs. |
| 20:22 | <jyasskin> | Domenic: Let me know if I definitely shouldn't define those helpers. :) |
| 20:34 | <jyasskin> | Is there any interest in an "ascii encode" next to https://infra.spec.whatwg.org/#isomorphic-encode that would assert all the codepoints are <=0x7f? |