Is there a reason you can’t capture from `new Promise` and just treat the resolution of that function (i.e., the function was called and resolve/reject was called) as if it were written as an async/await/throw function?
-
-
-
You mean take the stack trace at the `new Promise()` call site? Yes that would be possible, and that's what DevTools does, but it'd no longer be zero-cost. It's actually very expensive.
- Još 5 drugih odgovora
Novi razgovor -
-
-
:thinking_face: can we build a hack over this to fix the Async Hooks performance issue?
-
What's the relationship to async_hooks?
- Još 8 drugih odgovora
Novi razgovor -
-
-
"diagnosing _production_ issues" - does this mean there's currently some workaround for dev, a costly flag or something?
-
During development you can use the async stack traces feature in
@ChromeDevTools - Još 2 druga odgovora
Novi razgovor -
-
-
How can it be zero cost? You keeping some form of the stack around at every function invocation?
-
No, we use the information available in the promise chains. That approach is limited (since it'll only work as long as you stick to async functions and not do fancy Promise stuff by hand), but there's no added cost for that.
- Još 3 druga odgovora
Novi razgovor -
-
-
on which v8 version it expected to be shipped? what is the v8 tracking bug?
-
Flag is available starting with 7.2. tracking bug is http://crbug.com/v8/7522
Kraj razgovora
Novi razgovor -
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.
probably broke the web for you at least once
opinions are my own
&
& 
First working prototype of zero-cost async stack traces in 