Do and Block Params expressions [Parser]
See original GitHub issueFeature Request
Describe the solution you’d like
I suggest making do
and block param expressions. do
expression:
do {
// code
}
And block params:
something {
// code
}
something(someValue) {
// code
}
something(someValue) // one line of code
something // one line of code
a.b['c']('d')('e') {
// code
}
do
expression is already in stage 1 and so is Block params. So why not adding it? Pipeline operator is in stage 1, yet here we have it in Babel. I think that at least do
expressions should be in Babel.
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Parsing Expressions - Crafting Interpreters
In this chapter, you will attain it. “Parse” comes to English from the Old French “pars” for “part of speech”. It means to...
Read more >Understanding Ruby's block/proc parsing - DEV Community
The first expression list is the non proc arguments to the call. Passing a block. Imagine we call the method as: some_method {...
Read more >The Parser (page 2)
Parsing Code Structures · Code block · Assignment statements · Procedure calls · If statements · Case statements · For loops · Do...
Read more >8. Spring Expression Language (SpEL)
The Spring Expression Language (SpEL for short) is a powerful expression language that supports querying and manipulating an object graph at runtime.
Read more >Is it possible to parse a PowerShell param block by using a ...
I search for a regular expression to extract a Powershell param block from a complete PowerShell script. [CmdletBinding()] Param( [Parameter( ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I remember that some tc39 members said that that proposal is unlikely to proceed as-is.
I’m closing this issue; not because we don’t want to support them, but becasue we already track proposals implementation status in another repository: https://github.com/babel/proposals/issues/53