Currently, %>>% does not seamlessly work with Pipe object (directly with its inner value). Consider to make them compatible with each other so that they can co-work like
However, it is not recommended to use both piping in one pipeline, and benchmark tests show that this feature may notably lower the performance of operator by up to 40% but the performance loss is insignificant in practical use for data manipulation.
But I think this feature will allow the mixed use of Pipe and %>>%, which is not a good way to use them. Push this only to feature/cowork and it is unlikely to go to 0.4.
Currently,
%>>%
does not seamlessly work withPipe
object (directly with its inner value). Consider to make them compatible with each other so that they can co-work likeThis will allow the resulted Pipe persist the feature of command chaining with
$
.However, it is not recommended to use both piping in one pipeline, and benchmark tests show that this feature may notably lower the performance of operator by up to 40% but the performance loss is insignificant in practical use for data manipulation.