proposal-pattern-matching
proposal-iterator-helpers
proposal-pattern-matching | proposal-iterator-helpers | |
---|---|---|
67 | 35 | |
5,344 | 1,242 | |
0.9% | 2.6% | |
9.0 | 5.0 | |
9 days ago | 22 days ago | |
HTML | HTML | |
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-pattern-matching
-
Coming to grips with JS: a Rubyist's deep dive
Note, however, that there is a proposal to add pattern matching to JS.
-
Level up your Typescript game, functionally - Part 2
There's an ECMAScript proposal that is in the works to add this feature to the language! It's going to look something like this.
-
Building React Components Using Unions in TypeScript
More importantly, TypeScript typically commits to build things into itself when the proposal in JavaScript reaches Stage 3. The pattern matching proposal in JavaScript is Stage 1, but depends on many other proposals as well that may or may not need to be at Stage 3 as well for it to work. This particular proposal is interested on pattern matching on JavaScript Objects and other primitives, just like Python does with it’s native primitives. These are also dynamic types which helps in some areas, but makes it harder than others. Additionally, the JavaScript type annotations proposal needs to possibly account for this. So it’s going to be awhile. Like many years.
-
Explicit Software Design. Preliminary Conclusions
For true™ functional programming in JS, native pattern matching and partial function application are missing (at least for now: 1, 2). For proper OOP, it lacks real interfaces and compile-time dependency injection.
-
TypeScript Is Surprisingly OK for Compilers
The proposal for pattern matching syntax seems more akin to what they're looking for.
https://github.com/tc39/proposal-pattern-matching
-
[AskJS] C# in every Node.js job posting?
There's a proposal to add something like that to JavaScript but it's been stuck in limbo since 2017 although there are libraries like ts-pattern which implement it already.
-
[AskTS] What do you think will be the future of runtime type checking?
I'll admit, it is easy to assert that the TypeScript language should not be involved in the matters of packages but I also wonder if we're moving towards a point where interfaces will be as common as namespaces and whether or not it would be sensible for the language to incorporate such type assertions into the language formally, after all, it already compiles to various forms of JavaScript and there is a stage 1 proposal submitted to the TC39 committee to give JavaScript pattern matching. If adopted, wouldn't it make sense to allow TypeScript to compile a type into a type guard for the native JavaScript pattern matcher?
- 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.
-
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.)
proposal-iterator-helpers
-
TC39: Add Object.groupBy and Map.groupBy
Global iterator type is coming: https://github.com/tc39/proposal-iterator-helpers
But a method named `groupBy` on iterators traditionally means a different thing: https://github.com/tc39/proposal-array-grouping/issues/51#is...
Global iterable type it's too late for, since there's many extant iterables in the language and on the web which don't have it in their prototype chain and can't reasonably be changed.
-
Lodash just declared issue bankruptcy and closed every issue and open PR
Very much agreed. The amount of mileage we get from using Spread (literally the ...) alone has been amazing. https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe... Iteration helpers is shipping soon, that'll be a huge help (async iteration helpers will be delayed for a while). https://github.com/tc39/proposal-iterator-helpers .
In the olden days, I feel like the codebases I worked on needed to use .apply() multiple times a week, to figure out some creative way of invoking functions. https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe... That's all gone now; I'd take even odds that 50% of my team knows .call and .apply.
Chrome 117 is shipping Object.groupBy() and that's gonna be a huge help in eliminating a lot of the last places we end up using lodash. https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...
-
It’s 2023. Start using JavaScript Map and Set
Once this https://github.com/tc39/proposal-iterator-helpers reaches browsers, I'm prob gonna be exclusively using Maps.
- Why I Like Using Maps (and WeakMaps) for Handling DOM Nodes
-
Updates from the 95th TC39 meeting
No, probably not. But with iterator helpers, you can do
-
All JavaScript and TypeScript features of the last 3 years explained
> focus more on improving the terrible JS web API
That's W3C’s job, not ECMA’s.
> Where are all the containers?
?
> Sorted sets/maps?
Sets and Maps are sorted (by insertion order)
> Why can't I even map an iterator?
It's coming, but someone will likely be exhausted by that addition. https://github.com/tc39/proposal-iterator-helpers
-
Uncle Bob and Casey Muratori Discuss Clean Code
Upcoming: https://github.com/tc39/proposal-iterator-helpers
-
[AskJS] Is JavaScript missing some built-in methods?
Not Generators, but Iterators have a Stage 3 proposal with helpers like these.
-
Just fighting URLSearchParams and wonder if anyone uses iterators IRL and what I do miss
I guess you are not the only one dealing with this. That’s why there is this proposal https://github.com/tc39/proposal-iterator-helpers So hopefully it will get easier soon. But in most cases you can simply wrap it in Array.from or you can also clone with the spread operator.
-
Iterator/Generator Exercises?
Let's assume Number.range(), iterator helpers and some isPrime() function. From that we could easily create the following:
What are some alternatives?
fp-ts - Functional programming in TypeScript
proposal-function-helpers - A withdrawn proposal for standardizing some useful, popular helper functions into JavaScript’s Function object.
package.elm-lang.org - website for browsing packages and exploring documentation
IxJS - The Interactive Extensions for JavaScript
content - The content behind MDN Web Docs
proposal-hack-pipes - Draft specification for Hack pipes in JavaScript.
ecma262 - Status, process, and documents for ECMA-262
proposal-hack-pipes - Draft specification for Hack pipes in JavaScript. [Moved to: https://github.com/tc39/proposal-hack-pipes]
proposal-pipeline-operator - A proposal for adding a useful pipe operator to JavaScript.
EventSource - a polyfill for http://www.w3.org/TR/eventsource/
proposal-record-tuple - ECMAScript proposal for the Record and Tuple value types. | Stage 2: it will change!
mpr.kirke.dev