-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unification of pipe and fastpipe #1
Comments
It should be as easy as :
And maybe an alias |
It also need a Maybe discard That wouldn't be bad, because the And this way |
One problem is that I wanted a lightweight package with only one simple pipe, and here I have a lot, so we'll have to decide if we really move most to a pipes package, and which we keep here. I'm thinking maybe it's not that bad to have all here as long as we trim down the list of the pipes that exist in current pipes package. |
current list :
So that's only |
Will need also to copy and paste most of the tests with |
maybe get inspiration from |
not sure about this in the end |
We could incorporate the fast pipe in pipe.
It could be named
%>>%
and would have a special class and a good disclaimer.We'd remove the code handling functional sequences and compound operator (and thus the awkward option), so it'd be easy, we'd just use
%>>%
for programming and when we'd need robust behavior for lazy evaluation.We'd also add fast pipes
%T>>%
,%$>>%
, and%S>>%
.It's almost as easy to type, and no risk of confusion regarding functional sequences and compound ops.
And when we actually want to pipe
.
we can use%>>%
so an equivalent to functional sequences will be to use~ . %>>% fun()
in purrr style formulas.The text was updated successfully, but these errors were encountered: