A questions and a comment: 1. How will XDEBUG handle a multiline construct such as this? Will it treat as one expression, or allow breakpoints at each "link" in the pipe chain?
Maybe this is a better question for Derek Rethans? 2. The exclusive use of callable seems problematic prior to an inclusion a '::function' operator that can be applied to functions for symbol resolution to function name as it will encourage more use of strings that are not checked by PHP. Maybe we could address that first? Also #2 would be true for method names although how that might be implemented is a bit more complicated. -Mike > On Apr 20, 2020, at 9:38 PM, Larry Garfield <la...@garfieldtech.com> wrote: > > Hello fine people of Internals! > > I've been commenting on other RFCs enough lately that I should probably put > myself through the wringer, too. I therefore offer this RFC to add a > function pipe operator, as seen in a number of other languages: > > https://wiki.php.net/rfc/pipe-operator-v2 > > A patch is available here: > > https://github.com/php/php-src/pull/5425 > > Although I have one or two bits of it that I could use feedback on. (Let me > know over on GitHub.) > > It's deliberately a very small, lightweight, and targeted change. The Future > Work section suggests possible additions for later, but this is as much as my > meager skills can manage for the moment. > > My enormous thanks to Sammy K Powers and Levi Morrison for their copious > hand-holding in my first foray into php-src. > > *dons flame retardant suit* > > -- > Larry Garfield > la...@garfieldtech.com > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
