Hello world. The discussion has been dormant for a while. For now, I'm going to proceed with the simple-callable approach to pipes, rather than Elixir-style auto-partialling. I have also added a discussion of a possible future iterator API built for pipes to the RFC, and another example using stream resources and a few utilities to build lazy, self-cleaning stream processing chains. It actually looks really nice, I think. :-) Neither change the design or implementation.
Also, since Derick asked off-list, I am 90% certain that the current implementation will still allow Xdebug to "catch" on each step in a pipe chain, since at the opcode level it's just a bunch of function calls with anonymous intermediary values. And on the off chance it's not, I've been advised by other engine devs that the implementation is simple enough to tweak to make that work. So we're debug friendly. Baring any other feedback, I am going to open the vote Monday/Tuesday. --Larry Garfield
