I see a CL is in flight at https://chromium-review.googlesource.com/c/chromium/src/+/1319222. It seems like there is an incremental strategy in progress, instead of e.g. re-doing everything in idiomatic IDL and C++. For example a lot of usage of any, and only converting ReadableStream, not all streams classes at once.
Would someone mind summarizing the strategy, to better give context for reviews and spec work?
What I'm doing right now is "D: Introduce a thin ScriptWrappable"[1]. It's needed for TransferableStreams. Defining ScriptWrappable ReadableStream, WritableStream and TransformStreams is needed for the work.
Internal algorithms are still written in JavaScript at this stage. We will re-implement the logic in C++ probably in 2019.
https://docs.google.com/document/d/1_KuZzg5c3pncLJPFa8SuVm23AP4tft6mzPCL5at3I9M/edit#heading=h.egunr8797a77
Comment 1 by yhirano@chromium.org
, Nov 7