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
It'd be nice if we could get a stack traces without having to instantiate an Error (because sometimes we want a stack traces and instantiating an Error just for that isn't semantic).
f.e. this would be nice:
conststack=getStack()
Instead of
consterr=newErrorconststack=getStack(err)
And similar for getStackString.
The text was updated successfully, but these errors were encountered:
I'm torn between my desire for usability, and a desire to keep the spec lean, as this could easily be solved by a transpiler injecting new Error() between the parens, or a very simple library. In any case it should fail loudly if a passed-in variable happens to accidentially be undefined.
It'd be nice if we could get a stack traces without having to instantiate an Error (because sometimes we want a stack traces and instantiating an Error just for that isn't semantic).
f.e. this would be nice:
Instead of
And similar for
getStackString
.The text was updated successfully, but these errors were encountered: