proposal-pipeline-operator
proposal-do-expressions
Our great sponsors
proposal-pipeline-operator | proposal-do-expressions | |
---|---|---|
102 | 19 | |
7,330 | 1,042 | |
0.8% | 0.0% | |
2.7 | 0.0 | |
4 months ago | almost 3 years ago | |
HTML | HTML | |
BSD 3-clause "New" or "Revised" 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-pipeline-operator
-
Pipeline Operator great again!
Current Status: You'd have to check the TC39 proposals repository or the official proposal text for the most recent status. As of my last update, it had not yet reached Stage 4 (final stage) of the TC39 process, which means it wasn't part of the ECMAScript specification yet.
-
pipesAreFun
Javascript may get it https://github.com/tc39/proposal-pipeline-operator https://youtu.be/dQw4w9WgXcQ
-
JavaScript Gom Jabbar
It can be further simplified. For example, you don't need two separate functions to extract the first chat completion message etc.
This version:
- uses existing language constructs
- can be immediately understood even by the most junior devs
- is likely to be 1000 times faster
- does not rely on an external dependency that currently has 143 issues and every two weeks releases a new version adding dozens of new methods to things
Note: one thing I do wish Javascript adopted is pipes: https://github.com/tc39/proposal-pipeline-operator
-
What's new in ES2023?
Still in stage 2 atm https://github.com/tc39/proposal-pipeline-operator
- lizod - spiritual successor of zod less than 1kb
- Updates from the 96th TC39 meeting
-
Mostly adequate guide to FP (in JavaScript)
Both are active tc39 proposals :)
https://github.com/tc39/proposal-pipeline-operator - Stage 2
https://github.com/tc39/proposal-pattern-matching - Stage 1
Hopefully we get both in the next couple of years.
-
Tipe - typed pipe
Some time ago I saw how hyped JS community was about pipeline operator proposal. So I tried to make something similar in python. There is how tipe module was created. Check it out if you are interested: https://github.com/mishankov/tipe
-
CoffeeScript for TypeScript
We often add promising TC39 proposals into Civet so people can experiment without waiting.
We've added https://github.com/tc39/proposal-pipeline-operator, a variant of https://github.com/tc39/proposal-pattern-matching, a variant of https://github.com/tc39/proposal-string-dedent and others.
Since our goal is to be 99% compatible with ES we'll need to accommodate any proposals that become standard and pick up anything TC39 leaves on the table (rest parameters in any position, etc.)
-
[AskJS] Is JavaScript missing some built-in methods?
The Proposal is for the Hack pipe, so your example would be
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.
-
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
-
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.
-
[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:
There is an (early) proposal for do blocks in JavaScript which would be similar.
- 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:
-
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
-
What's the ternary operator alternatives?
The Do Expression proposal could help here: https://github.com/tc39/proposal-do-expressions
What are some alternatives?
ionide-vscode-fsharp - VS Code plugin for F# development
content - The content behind MDN Web Docs
FiraCode - Free monospaced font with programming ligatures
ramda - :ram: Practical functional Javascript
Gigablast - Nov 20 2017 -- A distributed open source search engine and spider/crawler written in C/C++ for Linux on Intel/AMD. From gigablast dot com, which has binaries for download. See the README.md file at the very bottom of this page for instructions.
proposal-partial-application - Proposal to add partial application to ECMAScript
Statsd - Daemon for easy but powerful stats aggregation
proposal-pattern-matching - Pattern matching syntax for ECMAScript
remeda - A utility library for JavaScript and TypeScript.
Escalin
proposal-function-helpers - A withdrawn proposal for standardizing some useful, popular helper functions into JavaScript’s Function object.
TypeScript - TypeScript is a superset of JavaScript that compiles to clean JavaScript output.