Anatoly Ressin

I still think that this PR is independent of #3582 The only thing that we should agree that `save` and `destroy` should always return thenables. Thus, if we combine this...

So why Deferred? Why not Backbone.Promise? And use pretty sandard `Backbone.Promise.resolve(value)` and `Backbone.Promise.reject(reason)` ? There is widespread belief that you should avoid using deferreds at all.

I would strongly advocate for the `Backbone.Promise` that should provide only two static methods `resolve` and `reject` ``` TypeScript declare module Backbone { ... export interface Thenable { then( fulfilled:...

Get here while googling for a commplex-link (5001) conflict with ipfs daemon. So the problem is actual.

@metaweta any news? If you need any help/discussion I would be glad to brainstorm on this issue. I really want this feature.

Now I have time to implement such a simple PR Hope to get some hints frome core devs, but there are no questions so far - all looks good and...

@mindeavor - imagine that you already have an implementation of the virtual method you need in some other class (i.e. Array). ``` TypeScript var {map} = Array.prototype; var anchors =...

Or even return to the earlier proposal for the foreign properties (not a bind at all for the obj::prop) ```js var prop1 = Symbol(); var prop2 = { get: function()...

@InvictusMB, it means only that we allow only the following syntax: PrimaryExpression "::" PrimaryExpression "(" ArgumentList ")" And treat foo::bar(a,b,c) as bar.call(foo, a, b, c) Standalone foo::bar is prohibited (not...

And yes, it is kind of pipelining, but it uses a hidden **this** parameter. I feel, that TC39 has very strange implicit resistance against any improvements related to any **this**...