blinry on Nostr: nprofile1q…atzsc I watched your brilliant Pipeline talk from NDC – and wanted to ...
nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqaff84v8ky3pyrnms23wlzjnzuurxjwewprzlf63h8evu5ctm7c2qvatzsc (nprofile…tzsc) I watched your brilliant Pipeline talk from NDC – and wanted to ask you something:
In a project, the concept of "bidirectional pipes" seems to come up a lot. They take input from both sides, and can send output to both sides. All four types can be different, and if input is invalid, the pipe might immediately send an error back!
See this example in Rust of a bytes-to-numbers pipeline: https://github.com/blinry/sans-io-pipe-example/blob/main/src/main.rs
Have you seen similar approaches, from which I could take inspiration?
In a project, the concept of "bidirectional pipes" seems to come up a lot. They take input from both sides, and can send output to both sides. All four types can be different, and if input is invalid, the pipe might immediately send an error back!
See this example in Rust of a bytes-to-numbers pipeline: https://github.com/blinry/sans-io-pipe-example/blob/main/src/main.rs
Have you seen similar approaches, from which I could take inspiration?