proposal-temporal VS proposal-bind-operator

In the TypeScript/JavaScript world the only thing called "Temporal" that I was aware of is the Stage 3 proposal for an excellent new date and time module:

https://tc39.es/proposal-temporal/docs/

Time Zone Canonicalization: Stacked on Temporal to improve handling of changes to the IANA Time Zone Database.

Roll-on Temporal!

There is a list of polyfills at the bottom of the page that can be used in production. https://github.com/tc39/proposal-temporal

TemporalJS is in stage 3 (of 4) of being pulled into the JavaScript standard lib. It really can't come soon enough...

There was also a different proposal that allows objects to be extended: https://github.com/tc39/proposal-bind-operator

Personally, I don't use classes much, but sometimes I think free functions a little bit hard to find, so I tend to experiment with the following pattern.

interface User { … }

const User = {

Yangi bind operatori Function.prototype.bind ni yanada elegant tarzda ishlatish imkonini beruvchi yangi sintaksis

In modern JS, you can export each function directly without putting them in an object. It also allows you to call a function with a specific “this” value, function.bind(object)(args). As a matter of fact, there’s a syntax proposal proposal and to do exactly this, object::function(args). This proposal could make what you describe pretty popular.

Hey, not yet ;)

This binding syntax (::)

You'd need 4 periods.

I don't think you want realms so much as protocols or extensions, the latter assimilating the beloved bind operator.