-
Notifications
You must be signed in to change notification settings - Fork 55
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
suggestion - @chainWithRTransform #325
Comments
I'm coming around to this being a good idea. It would certainly cut down on lots of typing and it definitely seems to be true that 90% of commands are Maybe @nalimilan can chime in and give their thoughts. Because this would be a pretty non-standard syntax transformation. |
How would it combine with grouping/ungrouping data frames in the process (I think it would be OK, but I want to make sure) |
Technically, would it be possible to support passing macro calls like That would make #376 a bit less ad-hoc. |
@bkamins I think it would only apply to row-wise operations, so grouping would in general be ignored. @nalimilan I'm not sure how that would work, are you saying something like
or something else? I also disagree what #376 ( |
@bkamins Maybe a better way to think of it:
So this
becomes
Its just a bit of Syntax Sugar |
So the first assignment operation present in the block drops grouping. |
Lines of the form
becomes
|
Yeah. It would drop grouping. |
Are you guys still interested in implementing this? |
A macro similar to @chain but treats any line that isn't another macro as being within an @rtransform @astable block. So what would currently be written as:
Could be written as:
The text was updated successfully, but these errors were encountered: