-
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
Allow for keyword arguments #179
Comments
Update, this is actually very easy to do without deciding |
I think this should go in before 1.0, and it should be the last thing we do before 1.0. Proposal: With the normal function call syntax |
Can you please show an example?
Other than that it looks reasonable |
Only once, at the end.
At the end
I think I would have
No. In call syntax they can just do |
So why do you need:
and not just e.g.:
? |
|
Then why not?
and allow it multiple times and require passing only one kwarg per line? |
Having keyword arguments would be very helpful. I just reverted a bunch of my code from DataFramesMeta.jl to DataFrames.jl when I realized that I cannot use |
Ah I'm sorry. I will try to finish this PR this week. It stalled due to a busy summer. |
DataFrames.transform
allows for keyword arguments. The current way@transform
parses expressions does not allow for this.Side note: this is a point for
:x
overx
, but we definitely want to allow keyword arguments.The text was updated successfully, but these errors were encountered: