proposal-bind-operator VS proposal-json-modules

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.

In the future we should be able to do this without the help of bundlers. For more information on that proposed feature, see: https://github.com/tc39/proposal-json-modules

Note that you'll need to specify the json import assertion here to import this as a JSON module

Import types other than JS. Some other files are in the pipeline JSON, but it will be a long time before we get it in the browser.

JSON Modules

JSON modules: ability to import a JSON module in a common way across JavaScript environments.