Sami Vaarala
Sami Vaarala
C code would call an Ecmascript function registered into the global stash, and that would call a Promise callback. But the callback would not have access to the function (except...
So _how_ would the application detect the wrapping call in this case - in concrete terms?
But I still don't understand what you mean by an "indirect" side effect here? What would such a thing be in concrete terms? What code could fail?
So what I'm trying to get at is that specifications in general specify external behavior. Anything consistent with that external behavior is generally acceptable (security features like memory wiping etc...
But that's a totally different case than what I'm talking about? I'll try to clarify: Consider first a case where promises are resolved from the top level. For example, the...
Note that I agree completely it's generally unsafe to resolve promises from wherever and if you do that things will fail in various ways. I'm just saying that the requirement...
> As long as no application calls are in progress when all that happens, then I would almost certainly deem that acceptable, even if it borders on being a Rube...
I meant what you mean by "Rube Goldberg" machine? :)
As a practical example (and one motivation why I'm trying to explain my view re: the call stack being empty): it would be hypothetically an OK first step to take...
No offense taken, I was just genuinely confused why you'd consider the setup contrived, because it appears (in essentially that form but with more actual meat) if an external Promises...