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

[question]: Progress on deciding operator precedence #172

Closed
KilianKilmister opened this issue Sep 4, 2020 · 1 comment
Closed

[question]: Progress on deciding operator precedence #172

KilianKilmister opened this issue Sep 4, 2020 · 1 comment

Comments

@KilianKilmister
Copy link

I'm working on a JS/ES like shell grammar for commandline use. and for that, a Pipeline Operator is obviously a must. and since i would like to use the same operator precedences as JS to make usage easier for js programmers, i wan't to consider what this proposal states precedence should be.

In the proposal it stated:

The precedence of |> sits between the ternary operator and ||. It is left-associative. bug

But the linked discussion hasn't come to any conclusion. Has there been any progress on that so far?

I commented my opinion in #23

@KilianKilmister KilianKilmister changed the title [question]: how confident is the current operator precedence [question]: Progress on deciding operator precedence Sep 4, 2020
@tabatkins
Copy link
Collaborator

Closing this issue, as the proposal has advanced to stage 2 with Hack-style syntax. (The precedence of |> is the same as =>.)

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 12, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants