You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
KilianKilmister
changed the title
[question]: how confident is the current operator precedence
[question]: Progress on deciding operator precedence
Sep 4, 2020
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:
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
The text was updated successfully, but these errors were encountered: