Jeremiah Senkpiel
Jeremiah Senkpiel
Due to potential conflicts with `iterator#next()`, perhaps this part of the protocol should be renamed. Any thoughts? Maybe something like `give()`?
I probably have enough material, could be good for visibility?
Refs: https://github.com/Fishrock123/bob/issues/23
It could expose `StdioSink(fd)` with shortcuts to fd 1/2 via `StdoutSink` and `StderrSink`. Might be better done outside of this repo.
I think it would be useful soon have a voice meeting to discuss various unresolved conversations. Things that should be talked about: - Project Approach evaluation - Goals evaluation -...
I think Stream() would be a good place for this, what does everyone else think? We should also be sure to handle cases such as https://github.com/nodejs/node/issues/28194
Binding is ugly and I bet it is the least comprehensible part right now. Ideally I guess it would look something like `Stream(source, transform, sink)`.
Not really super into moving stuff into an official repo atm but once some more status has been completed (see https://github.com/Fishrock123/bob/issues/2), we may want to so as to get some...
From the collab summit, after talking with @jasnell extensively about QUIC, I think it would be useful to have pull support an offset to ask the source to read from...
need to do this... currently it's really just done via the C++ passthrough