-
Notifications
You must be signed in to change notification settings - Fork 30
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
:: conflicts with E4X #27
Comments
A not-so-serious suggestion: |
From the looks of it, @zenparsing, the champion behind the operator, will not be supporting it. Instead, he's proposing "function pipelining". Something like: // Letting `foo`, `bar`, and `baz` be functions that return an array
arrayOfNumbers
->foo(el => el*2)
->bar(el => el*3)
->baz(el => el - 3) You can read about it at issue #26. |
Let's not worry about E4X for now. Thanks! |
This was referenced Jul 13, 2016
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The operator
::
is already used in E4X. It's true that E4X is deprecated and we rarely hear real world usage of it, but js2-mode provides editor support, so when implementing this I had to partially drop E4X support.I think it better to discuss here whether or not to continue with
::
and to be incompatible with E4X; btw..
as suggested by #10 also conflicts.@dgutov is the active collaborator there, who may have an idea whether E4X support is actually used by anyone.
The text was updated successfully, but these errors were encountered: