proposal-relative-indexing-method
proposal-object-freeze-seal-syntax
Our great sponsors
proposal-relative-indexing-method | proposal-object-freeze-seal-syntax | |
---|---|---|
12 | 2 | |
337 | 59 | |
- | - | |
4.3 | 0.0 | |
over 2 years ago | about 6 years ago | |
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-relative-indexing-method
-
Stop using Array[index], use Array.at() instead
If you want to learn more, check out the MDN reference for it. You can also read the original proposal for it.
- ECMAScript 2022 introduces at() method in Array, String, TypedArray
-
Learning the new `at()` function, at #jslang
Just like every other array method, it’s type coerced. It’s a problem with all built ins, best not fracture this more in JS without a very good reason. https://github.com/tc39/proposal-relative-indexing-method/issues/40
-
10+ Interesting ECMAScript Proposals
.at()
-
Updates from the 85th meeting of TC39
.at() .at() method on all the built-in indexables.
-
Javascript ES2021 Summary
For a proposal to be finalized, it needs "Two compatible implementations which pass the acceptance tests" (source). This can mean browsers but also includes transpilers like babel. Chrome - which also includes other browsers now like Edge and Opera - will often release stage 3 features publicly before finalized, and Firefox isn't usually far behind, or sometimes even first, as was the case with the currently stage 3 at() method for arrays. Safari is probably the one you have to worry about the most. They tend to be further behind, I think mostly due to their release cadence being longer. Safari, for example, doesn't yet support private methods whereas the other browsers have supported them for some time now. While private methods are stage 4, they are expected to be part of ES2022 which hasn't been published yet - the current being ES2021.
-
Can I use .length -1 to call a string value?
Soon we’ll get this nicer version (proposal):
-
Stage 3 Proposal: Array.prototype.at
Proposal hosted on GitHub explains the reasoning behind it https://github.com/tc39/proposal-relative-indexing-method
-
Array Indexing Method
https://github.com/tc39/proposal-relative-indexing-method#rationale
proposal-object-freeze-seal-syntax
-
10+ Interesting ECMAScript Proposals
Object freeze and seal syntax: {# ... #} or {| ... |}
-
Can we get the exact same experience with functions but without use of any classes?
There has been a proposal for frozen/sealed syntax for object literals which would make this a lot more concise in that context, but this is the same syntax being proposed for the record/tuple proposal, so I doubt that's going anywhere anytime soon.
What are some alternatives?
proposal-temporal - Provides standard objects and functions for working with dates and times.
proposal-partial-application - Proposal to add partial application to ECMAScript
proposal-array-last - A JavaScript TC39 Proposal for getting the last element from an array
proposal-bind-operator - This-Binding Syntax for ECMAScript
proposal-decimal - Built-in decimal datatype in JavaScript
proposal-as-patterns - `as` destructuring patterns
proposal-shorthand-improvements - A proposal to introduce new shorthand assignment forms for ECMAScript object literals
proposal-generator-arrow-functions - ECMAScript proposal: Generator Arrow Functions
proposal-array-from-async - Draft specification for a proposed Array.fromAsync method in JavaScript.
reify - Enable ECMAScript 2015 modules in Node today. No caveats. Full stop.