| 12:28 | <TabAtkins> | Yeah, the working copy is still duplicated, but you can at least avoid duplicating the *rest* of history. |
| 12:37 | <nox> | I don't think GH does anything fancy, it just has all forks share a single repository AFAICT. |
| 12:39 | <nox> | (For example you can access any upstream commits that are not yet supposed to be in your fork, from the fork's page on GH.) |
| 21:57 | <devsnek> | is there any way to entangle an existing readable and writable into a transform |
| 22:35 | <TimothyGu> | devsnek: can you give a use case? |
| 22:38 | <devsnek> | TimothyGu: i'm working on interop with node streams |
| 22:38 | <devsnek> | i have a method to get a readable stream and a method to get a writable stream |
| 22:38 | <devsnek> | i'd like to just entangle them |
| 22:39 | <devsnek> | the transform stream constructor doesn't let you specify stuff like the pull method of readable etc |
| 22:40 | <TimothyGu> | well you have to assign semantics to how they are entangled no? |
| 22:41 | <devsnek> | its kinda just readable.read().then(transform).then(writable.write) right? |
| 22:41 | <TimothyGu> | oh, isn’t that pipeTo then? |
| 22:42 | <devsnek> | there's no way to pipeThrough without a transform stream |
| 22:42 | <devsnek> | i was just trying to describe the semantics of a transform stream |
| 22:42 | <TimothyGu> | pipeTo, not pipeThrough |
| 22:43 | <TimothyGu> | can you give me an example of what the “methods to return a readable stream and a writable stream” |
| 22:43 | <TimothyGu> | (also on a train so spotty internet) |
| 22:45 | <devsnek> | readable https://github.com/nodejs/node/pull/22352/files#diff-ba6a0df0f5212f5cba5ca5179e209a17R991 |
| 22:45 | <devsnek> | writable https://github.com/nodejs/node/pull/22352/files#diff-1915a7b992a3012b177dd855fa3477e0R594 |
| 22:45 | <devsnek> | here's my current impl of transform but i think its missing the proper support with node's impl of backpressure https://github.com/nodejs/node/pull/22352/files#diff-9d52ef7e808de6b37f6f25d758fe99d3R206 |