Re: [whatwg/streams] Exact normative requirements for interface definitions are unclear (#732)

@domenic

>Where do you find this IDL for Blink? Blink implements its Readable Stream implementation the same way it does its other ES-style builtins: https://cs.chromium.org/webrtc/src/third_party/WebKit/Source/core/streams/ReadableStream.js

I found it here:
https://chromium.googlesource.com/chromium/blink/+/master/Source/core/streams/ReadableStream.idl

I believe that is the canonical Blink repository, as it's referenced in the current Chromium checkout instructions. Your URL seems to be a pointer to a copy of WebKit inside webrtc, and, since it still uses the third_party/WebKit naming, I believe it's older than what I pointed to.

That said, I'm not an expert on Chromium. It's possible that I got the wrong repository, or that I'm looking at a currently unused Streams implementation, or something. If so, my mistake! But even if this implementation is not current, it shows that someone tried to reverse-engineer IDL once.

> Every other data property described in clauses 18 through 26 and in Annex B.2 has the attributes { [[Writable]]: true, [[Enumerable]]: false, [[Configurable]]: true } unless otherwise specified.

It was not obvious to me that a statement about ECMASCript specification clauses 18 through 26 and Annex B.2 would apply to content that is not only not in those clauses, but not even in the ECMAScript spec.

Is there any clause in the ECMAScript spec that would let a reader know that the `reason` parameter is optional? (Or is that a mistake in the IDL translation? Or in the spec?)

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/streams/issues/732#issuecomment-293490861