Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign upreconsider func-call-spacing #1208
Comments
This comment has been minimized.
This comment has been minimized.
stale
bot
commented
Jan 1, 2019
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
stale
bot
added
the
stale
label
Jan 1, 2019
This comment has been minimized.
This comment has been minimized.
|
?? |
stale
bot
removed
the
stale
label
Jan 1, 2019
This comment has been minimized.
This comment has been minimized.
stale
bot
commented
Apr 1, 2019
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
stale
bot
added
the
stale
label
Apr 1, 2019
stale
bot
closed this
Apr 8, 2019
lock
bot
locked as resolved and limited conversation to collaborators
Jul 9, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
smuemd commentedOct 3, 2018
What version of standard?
^12.0.1
What operating system, Node.js, and npm version?
OSX, node v8.9.3, npm v6.4.1
What did you expect to happen?
This is a proposal:
When applying a function,
These styles are currently allowed in standard
This proposes to also allow the following call styles (effectively not enforcing eslint rule http://eslint.org/docs/rules/func-call-spacing)
Rational
This addresses readability problems associated with
)(style when dealing with regular curried functions.For example:
(for more context see sanctuary-js/sanctuary#438)
Note that this has been previously discussed in issue #530
Reconsidering your stance on
func-call-spacingmay help better accommodate functional programming styles.