proposal-record-tuple VS proposal-decimal

relevant issue, which is at the crux of this problem: https://github.com/tc39/proposal-record-tuple/issues/387

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.

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

It will be called "record" in JavaScript which will swing the popularity back the other way I guess (currently a language proposal)

I suspect considering the strong desire to maintain consistency with JavaScript, we will eventually see something that when the Record proposal passes through tc39

I hope the Record and Tuple proposal makes it through

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.

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).

Record and tuple is at stage 2

Also, js has an ongoing immutable value data types proposal.

Bloomberg are currently sponsoring Igalia to work on adding native Decimal number support to JavaScript.

https://github.com/tc39/proposal-decimal

This is an active proposal and was last discussed in the September 2023 meeting.

would it be possible, for example, to access the standard decimal library of C# or Python via Javascript, thus not having to wait for the TC39 spec / implementation? [1]

[1] https://github.com/tc39/proposal-decimal

There's a BigDecimal TC39 proposal to bring this kind of thing to the native language, but until then you have to choose between accuracy and performance.

To solve the problem while JavaScript waits on its own BigDecimal API, you can use something like bignumber.js to perform your calculations.

TC39 is now advancing Built-in decimal datatype in JavaScript.

given the popularity of javascript, it's about time we had better native tools for dealing with numbers in general, but it seems like the discussion is very slow on this front. for instance, the decimal proposal is still at stage 1 [1]. and no, BigInt does not solve that.

[1] https://github.com/tc39/proposal-decimal

In the future, JavaScript will hopefully get base 10 arithmetic: https://github.com/tc39/proposal-decimal