You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently error reporting does keep track of every Rejected instance. ES7 promises (and afaik basically any other promise implementations) do however keep track of the promises (futures) that are rejected without handlers.
See tc39/ecma262#76 for more links.
The problem with Creed's current approach is that it does not detect branching. Consider the example
While Creed does report p to be handled, it should actually have reported q as unhandled in the first place.
This is not an easy problem for sure with the nearing approach, as with x = reject(…), y = new Future, z = new Future we would have to distinguish z.become(y); y.become(x) from z.become(x); y.become(x) (in any order).
Any thoughts?
I am not sure to what extent creed does use the standardised rejection tracking events, I kinda have lost track of proposals/implementations/specifications.
Btw, node has some nice tests here.
Also this issue will probably solve the matter of silencer being an Action, I'd expect silencing to see some major change.
The text was updated successfully, but these errors were encountered:
Currently error reporting does keep track of every
Rejected
instance.ES7 promises (and afaik basically any other promise implementations) do however keep track of the promises (futures) that are rejected without handlers.
See tc39/ecma262#76 for more links.
The problem with Creed's current approach is that it does not detect branching. Consider the example
While Creed does report
p
to be handled, it should actually have reportedq
as unhandled in the first place.This is not an easy problem for sure with the nearing approach, as with
x = reject(…), y = new Future, z = new Future
we would have to distinguishz.become(y); y.become(x)
fromz.become(x); y.become(x)
(in any order).Any thoughts?
I am not sure to what extent creed does use the standardised rejection tracking events, I kinda have lost track of proposals/implementations/specifications.
Btw, node has some nice tests here.
Also this issue will probably solve the matter of
silencer
being an Action, I'd expect silencing to see some major change.The text was updated successfully, but these errors were encountered: