proposal-explicit-resource-management
proposal-record-tuple
proposal-explicit-resource-management | proposal-record-tuple | |
---|---|---|
22 | 73 | |
703 | 2,428 | |
4.0% | 0.7% | |
6.5 | 2.7 | |
27 days ago | 5 months ago | |
JavaScript | HTML | |
BSD 3-clause "New" or "Revised" 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-explicit-resource-management
- Cooperation between Cloudflare Workers has become amazing thanks to RPC support
-
Proposal: Signals as a Built-In Primitive of JavaScript
The standard doesn't have anything to do with TypeScript, not sure where you got that from? https://github.com/tc39/proposal-explicit-resource-managemen...
-
How does TypeScript's explicit resource management work?
The explicit resource management proposal tries to make it a bit easier for us, by allowing the resource to declare how it should be managed, rather than expecting us to clean everything up when we use the resource. We get a new keyword using to define a variable (rather than const or let), which tells the runtime to clean up the resource at the end of the function.
-
Using using in TypeScript for resource management
Enter the explicit resource management proposal, which describes — among many other things — a new using operator that was introduced in TypeScript 5.2 and is making its way into JavaScript. From the top of the README file, here’s what this proposal aims to do:
-
OpenTelemetry in 2023
In addition to this, is the new (stage 3 even!)explicit resource management proposal[0], supported by TypeScript version >= 5.2[1]
Though I agree that async context is better fit for this generally, the RMP should be good for telemetry around objects that have defined lifetime semantics, which is a step in the right direction you can use today
[0]: https://github.com/tc39/proposal-explicit-resource-managemen...
[1]: https://www.totaltypescript.com/typescript-5-2-new-keyword-u...
- ECMAScript Explicit Resource Management Proposal
-
Why is JavaScript so hated?
It's too early for that, https://github.com/tc39/proposal-explicit-resource-management
-
TypeScript 5.2's New Keyword: 'using'
[3]: https://github.com/tc39/proposal-explicit-resource-managemen...
-
Douglas Crockford: “We should stop using JavaScript”
I'm not _entirely_ sure which RAII you mean, but if you mean something like C#'s `using` or Java's `try-with-resources` or Python's `with`, then https://github.com/tc39/proposal-explicit-resource-managemen... and https://github.com/tc39/proposal-async-explicit-resource-man... are in stage 3 (of 4 stages) in ECMAScript's language proposal lifecycle and will be coming to a JS engine near you behind a flag soon-ish.
proposal-record-tuple
-
Union, intersection, difference, and more are coming to JavaScript Sets
relevant issue, which is at the crux of this problem: https://github.com/tc39/proposal-record-tuple/issues/387
-
The Everything NPM Package
There are still so many basic things that aren't in the JS stdlib, though. A good example is Map - if you need to use a tuple of two values as a key, you're SOL because there's no way to customize key comparisons. Hopefully we'll get https://tc39.es/proposal-record-tuple/ eventually, but meanwhile languages ranging from C++ to Java to Python have had some sensible way to do this for over 20 years now.
-
Deep Cloning Objects in JavaScript, the Modern Way
If you’re reaching for structuredClone, what you really want is native immutable Record and Tuple syntax, and the companion “deep path properties” syntax which allows for efficient and ergonomic immutable updates:
- https://github.com/tc39/proposal-record-tuple
-
Cool language features that Rust is missing?
It will be called "record" in JavaScript which will swing the popularity back the other way I guess (currently a language proposal)
-
Why doesn't TypeScript properly type Object.keys?
I suspect considering the strong desire to maintain consistency with JavaScript, we will eventually see something that when the Record proposal passes through tc39
-
ES2023 features list!
I hope the Record and Tuple proposal makes it through
-
ES2023 introduces new array copying methods to JavaScript
I mean, I'd love some real immutable/persistent data structures in JS by default, or even some Immer-like syntax sugar. Something like the record/tuple proposal would be awesome.
-
What's new in ECMAScript 2023
This will become very useful once Records and Tuples are a thing, because it allows you to store object references in a record/tuple (which by definition can only contain primitives).
-
[AskJS] Is JavaScript missing some built-in methods?
Record and tuple is at stage 2
-
The huge potential of Kotlin/Wasm
Also, js has an ongoing immutable value data types proposal.
What are some alternatives?
caniuse - Raw browser/feature support data from caniuse.com
zod - TypeScript-first schema validation with static type inference
librope - UTF-8 rope library for C
Immer - Create the next immutable state by mutating the current one
pidove
typescript-eslint - :sparkles: Monorepo for all the tooling which enables ESLint to support TypeScript
proposal-class-method-parameter-decorators - Decorators for ECMAScript class method and constructor parameters
typescript-is
search-benchmark-game - Search engine benchmark (Tantivy, Lucene, PISA, ...)
TypeScript - TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
proposal-iterator-helpers - Methods for working with iterators in ECMAScript
proposals - Tracking ECMAScript Proposals