Skip to content
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

Functional forms and argument ordering #5

Closed
tshort opened this issue Mar 3, 2014 · 0 comments
Closed

Functional forms and argument ordering #5

tshort opened this issue Mar 3, 2014 · 0 comments
Labels

Comments

@tshort
Copy link
Contributor

tshort commented Mar 3, 2014

Many of the LINQ-like operations have a functional form where a function is passed as an argument, like:

where(g, d -> mean(d[:a]) > 0)

This form is quite common with LINQ libraries. The issue is argument ordering. Base Julia functions like map all have the function passed as the first argument. The LINQ standard uses the function as the second argument, and passing the "operations" as the second argument is more consistent with the macro form: @where(g, mean(:a) > 0).

Our choices are: (1) follow Julia base, (2) follow the LINQ standard, or (3) define both.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant