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

:: conflicts with E4X #27

Closed
XeCycle opened this issue Oct 15, 2015 · 3 comments
Closed

:: conflicts with E4X #27

XeCycle opened this issue Oct 15, 2015 · 3 comments

Comments

@XeCycle
Copy link

XeCycle commented Oct 15, 2015

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.

@XeCycle
Copy link
Author

XeCycle commented Oct 15, 2015

A not-so-serious suggestion: .* in C++ is similar to this in functionality.

@shovon
Copy link

shovon commented Oct 15, 2015

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.

@zenparsing
Copy link
Member

Let's not worry about E4X for now. Thanks!

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

3 participants