ecma262
proposal-iterator-helpers
Our great sponsors
ecma262 | proposal-iterator-helpers | |
---|---|---|
22 | 35 | |
14,730 | 1,224 | |
0.7% | 2.4% | |
9.0 | 5.0 | |
2 days ago | 17 days ago | |
HTML | HTML | |
GNU General Public License v3.0 or later | - |
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.
ecma262
- TC39: Add Object.groupBy and Map.groupBy
-
The "well-known" Symbols in JavaScript
These aren't valid JavaScript (@@iterator would throw an error). They are actually internal Symbols used in JavaScript. They are used to implement features like iteration, instanceOf, and such internally. They actually might get removed or changed
-
📦🔓Closures in JavaScript decoded
Note that in previous editions, the ECMAScript® Language Specification used the term "lexical environment" before it decided to rename it to "Environment Record" so you might encounter this term in other definitions and tutorials.
- Document.all Willful Violation
- ES2023 Candidate source code + specification
- ES2023 candidate source code + spec
-
The Evolution of JavaScript
For a new specification to be written, you need two things, a_ technical committee_, and a standard. The standard specification for JavaScript is called ECMA-262, and the technical committee is Technical Committee-39(TC39).
- Why Async/Await Is More Than Just Syntactic Sugar
-
Show HN: We are trying to (finally) get tail-calls into the WebAssembly standard
4. Proposed something else [ https://github.com/tc39/proposal-ptc-syntax ]
While apple is against Syntactic tail calls, they’re mainly just opposed to versions of it that would remove/unrequire the tail-call optimisation they already do: https://github.com/tc39/ecma262/issues/535
For the version of it that is backwards compatible, they wouldn’t need to do anything other than recognise it as valid syntax. Their main concern is that it "could add confusion with very little benefit."
-
What happened to proper tail calls in JavaScript? (2021)
The spec for STC has a critique of PTC:
- performance
- developer tools
- Error.stack
- cross-realm tail calls
- developer intent
See: https://github.com/tc39/proposal-ptc-syntax#issues-with-ptc
Apple's 2016 response as to why they won't implement STC is here: https://github.com/tc39/ecma262/issues/535
- STC is part of the spec and will take too long to change.
- Now that they've implemented support for PTC, they don't want to regress web pages that rely on it.
- They don't want to discourage vendors from implementing PTC by agreeing to STC.
- They don't want to introduce confusion.
Some of these arguments about confusion and delays seem wrong hindsight, since on every point things would have been better if they'd just agreed to the compromise of STC.
- It would have been part of the spec years ago
- STC would have had a clear way for web pages to know when tail calls could be relied on (and PTC would have been optional)
- Other vendors didn't implement PTC in any case, despite no agreement on STC
- There's even more confusion as things are now
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?
proposal-pattern-matching - Pattern matching syntax for ECMAScript
proposal-function-helpers - A withdrawn proposal for standardizing some useful, popular helper functions into JavaScript’s Function object.
spec - WebAssembly specification, reference interpreter, and test suite.
IxJS - The Interactive Extensions for JavaScript
proposal-ptc-syntax - Discussion and specification for an explicit syntactic opt-in for Tail Calls.
proposal-hack-pipes - Draft specification for Hack pipes in JavaScript.
TypeScript - TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
proposal-hack-pipes - Draft specification for Hack pipes in JavaScript. [Moved to: https://github.com/tc39/proposal-hack-pipes]
io-ts - Runtime type system for IO decoding/encoding
EventSource - a polyfill for http://www.w3.org/TR/eventsource/
uwm-masters-thesis - My thesis for my Master's in Computer Science degree from the University of Wisconsin - Milwaukee.
mpr.kirke.dev