One of the primary issues with programming with pipes is that debugging on the fly gets a lot nastier when working with long(ish) pipe chains. For instance I find that the only way to debug an error in a long chain of pipes is to do the following,
data %>>% ... %>>% (~browser()) %>>% ...
But that involves modifying the code as opposed to just running a debug command.
Could a feature similar to the debug function be implemented that serves the same purpose for the pipe operator?
One of the primary issues with programming with pipes is that debugging on the fly gets a lot nastier when working with long(ish) pipe chains. For instance I find that the only way to debug an error in a long chain of pipes is to do the following,
But that involves modifying the code as opposed to just running a
debug
command.Could a feature similar to the
debug
function be implemented that serves the same purpose for the pipe operator?