--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAC_ixdx5m4gY61XXOvwDwvpxdHAXSCmznSe63PMPe2KhPHUrWA%40mail.gmail.com.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscribe@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAC_ixdx5m4gY61XXOvwDwvpxdHAXSCmznSe63PMPe2KhPHUrWA%40mail.gmail.com.
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CACj%3DBEgAyng3uMYH9oWTvUc8wbxh0MFzqkTXbX9dtNrQt-VYdg%40mail.gmail.com.To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscribe@chromium.org.
Unification of WHATWG Streams with the concept of a stream used in the Encoding Standard. Despite having the same name, they are different in functionality and purpose. Since the Encoding Standard's "stream" concept is just an internal piece of spec terminology, this has no impact on developers.
It's actually not clear from the explainer that the streams in this specification refer to WHATWG Streams. Adding a sentence saying that somewhere close to this paragraph would make it (even more) obvious.