proposal-do-expressions
proposal-slice-notation | proposal-do-expressions | |
---|---|---|
2 | 19 | |
518 | 1,066 | |
0.4% | 2.3% | |
0.0 | 0.0 | |
5 months ago | about 3 years ago | |
HTML | HTML | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
proposal-slice-notation
-
HypeScript: Simplified TypeScript's type system in TypeScript's own type system
> Switch statements
JS has had switch statements for a long time. Do you mean switch "expressions" that can be used inline? It's not pretty but JS has long supported that too using either eval() "hacks" or IIFEs: https://stackoverflow.com/questions/32451049/is-eval-the-onl...
Do you mean pattern matching? There are two Stage 1 TC39 proposals with different approaches to it:
More hands-on/direct: https://github.com/tc39/proposal-pattern-matching
More indirect: https://github.com/tc39/proposal-do-expressions
> list comprehensions
There are several libraries with strong Iterator support today that while not syntactically gorgeous do great jobs at allowing you to write simple list operations. Off the top of my head are IxJS and iter-tools, but also classic mainstays like up to date versions of lodash and Ramda.
There's a Stage 2 proposal to bring more of them into "the standard library": https://github.com/tc39/proposal-iterator-helpers
There's also a Stage 2 proposal for an operator to make the syntax generally nicer no matter the library: https://github.com/tc39/proposal-pipeline-operator
> array slicing
Array.prototype.slice() was added back in ES2015: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...
Array.prototype.at() was "just added" in ES2022 for unary "slice" (ability to use negative indexes): https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...
If you prefer syntax to function calls, there's a Stage 1 proposal still live for that: https://github.com/tc39/proposal-slice-notation
> better equality operators
That ship has probably sailed. Most projects at this point just have linter rules to standardize everything to the more reliable "triple equals" (===, and !==).
There are proposals for more structural equality functions in the standard library, though, for instance: https://github.com/tc39/proposal-array-equality
-
JavaScript Is Weird
Both are stage 1 proposals that I hope get in there some day.
https://github.com/tc39/proposal-slice-notation
https://github.com/tc39/proposal-pattern-matching
proposal-do-expressions
-
TypeScript Is Surprisingly OK for Compilers
> no pattern matching/switch expressions
They're still waiting on the do expression proposal for that (https://github.com/tc39/proposal-do-expressions), which has been in the bikeshedding stage for the past five years.
-
[AskJS] Opinions on using self executing functions as multi-line expressions.
At some point, it may be superseded by do blocks, but for now it's really your best bet.
-
What is this called? { id ? <Dashboard/> : <Login/> } and can I make it check for multiple things like a switch case?
But there is a proposal for do-expression : https://github.com/tc39/proposal-do-expressions
-
Using {Blocks} in Rust & Go for Fun & Profit
It's also the reason why do expressions are my most anticipated feature for JS.
-
Pipe Operator (|>) For JavaScript
> They should repurpose `do` so that `do {}` (without the `while`) is an expression that you can put statements inside and return the last statement.
There's a proposal for precisely that. Unfortunately, only Stage 1 though.
https://github.com/tc39/proposal-do-expressions
- Is a single ternary operator inside the returned JSX acceptable?
-
[AskJS] Is there ever a good use for loose blocks in JS?
It's one of the main reasons why I really want the do-expression propsal to work out, because then it would become:
- The TC39 Process
-
[AskJS] What are still present issues in contemporary (2022) JavaScript?
Do blocks. Okay, this is actually a proposal so maybe someday. Basically blocks that can resolve to an expression.
-
'The best thing we can do today to JavaScript is to retire it,' says JSON creator Douglas Crockford • DEVCLASS
Tomorrow, do expressions:
What are some alternatives?
Super-Template-Tetris - Tetris as a C++ Template Metaprogram
native-messaging-bash - Bash Native Messaging host.
V7 - Embedded JavaScript engine for C/C++
captureSystemAudio - Capture system audio ("What-U-Hear")
proposal-array-equality - Determining Array Equality
proposal-pipeline-operator - A proposal for adding a useful pipe operator to JavaScript.
coffeescript - Unfancy JavaScript
proposal-upsert - ECMAScript Proposal, specs, and reference implementation for Map.prototype.upsert
devtools-detect - Detect if DevTools is open and its orientation
caya - a tiny useful simple language experiment
proposal-pattern-matching - Pattern matching syntax for ECMAScript