We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Could it make sense to make arguments syntax for-like? Instead of writing
// ... this is what you write ... a(1) do (foo) { // ... } // ... this is what you get ... a(1, (foo) => { ... })
we could write
a(let foo of 1) { // ... } // means a(1, (foo) => { ... }) a(let [foo, bar] of 1, 2) { // ... } // means a(1, 2, ([foo, bar]) => { ... }) a(let foo, bar of 1, 2) { // ... } // means a(1, 2, (foo, bar) => { ... }) a(const foo, bar of 1, 2) { // ... } // means a(1, 2, (__foo__, __bar__) => { const foo = __foo__, bar = __bar__ ... })
Or we can use other separator between arguments lists. E.g. ;:
;
a(let foo; 1) { // ... } // means a(1, (foo) => { ... }) a(let [foo, bar]; 1, 2) { // ... } // means a(1, 2, ([foo, bar]) => { ... }) a(let foo, bar; 1, 2) { // ... } // means a(1, 2, (foo, bar) => { ... }) a(const foo, bar; 1, 2) { // ... } // means a(1, 2, (__foo__, __bar__) => { const foo = __foo__, bar = __bar__ ... })
The text was updated successfully, but these errors were encountered:
Hmmm.. may be the for keyword could be better for that:
for
a(let foo for 1) { // ... } // means a(1, (foo) => { ... }) a(let [foo, bar] for 1, 2) { // ... } // means a(1, 2, ([foo, bar]) => { ... }) a(let foo, bar for 1, 2) { // ... } // means a(1, 2, (foo, bar) => { ... }) a(const foo, bar for 1, 2) { // ... } // means a(1, 2, (__foo__, __bar__) => { const foo = __foo__, bar = __bar__ ... })
Sorry, something went wrong.
No branches or pull requests
Could it make sense to make arguments syntax for-like?
Instead of writing
we could write
Or we can use other separator between arguments lists. E.g.
;
:The text was updated successfully, but these errors were encountered: