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

> 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.

Sorry about that. I just grabbed the first ReadableStream.js that I found. The correct one is https://cs.chromium.org/chromium/src/third_party/WebKit/Source/core/streams/ReadableStream.js. Adam has explained the confusion about third_party/WebKit inside Chromium vs. Blink

> 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?)

In ES it works the other way around. You have to explicitly choose to throw if something is undefined. Since there is no line "If reason is undefined, throw a TypeError", it is optional. It's all very explicit; no implicit throwing like Web IDL has. Again, this is tricky for people coming into it with expectations from other standards that WHATWG produces, and we didn't realize that there would be such a standards-org <-> assumptions about implicit spec behavior tie when we started this project.

-- 
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-293596345