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

Establishing Guidelines for Maximizing Anonymous Function Readability in Reference to Escaped and Expanded Notations #171

Open
ghost opened this issue Apr 7, 2018 · 3 comments

Comments

@ghost
Copy link

ghost commented Apr 7, 2018

No description provided.

@christopheradams
Copy link
Owner

"Readability" can be subjective. Can you think of some examples that would illustrate the guideline? Also, I'd probably phrase this in terms of anonymous functions rather than lambdas, to keep it in line with the official docs.

@ghost
Copy link
Author

ghost commented Apr 9, 2018

If the position of the elements or operations in the anonymous function define the variables, then I would say an expanded anonymous function is redundant. For example,

f = &(&1 + 1)
# and 
g = &([&2 | &1])

are both defined wholly by their form, without variable names. You can look at each of these and see that f is an increment function and g is a reversal function. Especially if you're piping into them.

@ghost ghost changed the title The capture operator should be used over expanded lambda notation unless the variable names are essential for readability The capture operator should be used over expanded anonymous function notation unless the variable names are essential for readability Apr 9, 2018
@ghost ghost changed the title The capture operator should be used over expanded anonymous function notation unless the variable names are essential for readability Establishing Guidelines for Maximizing Anonymous Function Readability in Reference to Escaped and Expanded Notations Apr 9, 2018
@christopheradams
Copy link
Owner

I think we can state a preference for using the capture operator when defining an anonymous function for a known function and arity.

However, in the case of using the capture operator for partially applied functions with placeholder values, I'm not confident there could be a hard and fast rule for when variable names are "essential for readability".

I understand your point that anonymous functions that use simple operators or list operations don't need to be written out fully using fn... end. If you can write up a style rule that expresses it, I would consider it.

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

No branches or pull requests

1 participant