Promise.cancel()

Would it be consistent in 3.0 to add static Promise.cancel() to return a new promise in cancelled state? (like Promise.resolve() and Promise.reject())

Promise.cancel = function() {
      var p = Promise(function(){});
      p.cancel();
      return p;
}

[Artazor]

Even more surprising is that now

var a = request("A"); // from the previous example
var p = a.then(function(res) {
    console.log("fulfilled:", res);
    p.cancel(); // break the chain early
}).then(function() {
    console.log("Called")
});

produces

fulfilled: {body: "A"}

so the chain is broken.

But the same code with Promise.resolve({body: "A"})

var a = Promise.resolve({body: "A"});
var p = a.then(function(res) {
    console.log("fulfilled:", res);
    p.cancel(); // break
}).then(function() {
    console.log("Called")
});

produces:

fulfilled: {body: "A"}
Called

So the chain is not broken

O_o? (bye-bye mocked requests in unit/integration tests?) Worth it to be registered as a new issue?

[petkaantonov]

@benjamingr cancellation isn’t rejection with cancellation in 3.0