| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
There was a problem hiding this comment.
Either
| it helps associating method calls that otherwise do not appear together | |
| it helps with associating method calls that otherwise do not appear together |
or
| it helps associating method calls that otherwise do not appear together | |
| it helps associate method calls that otherwise do not appear together |
That being said – what’s a typical call stack?
Sorry, something went wrong.
There was a problem hiding this comment.
@addaleax , I used typical here to mean a representative call stack on node.js program error. As per my understanding, a representative stack is a incomplete part of an asynchronous sequence. Am I wrong?
Sorry, something went wrong.
There was a problem hiding this comment.
@HarshithaKP I’m still confused… That kind of only moves the question from “what’s a typical call stack?” to “what’s a representative call stack?”.
To be honest, I think it’s okay to drop the second sentence here. The sentence is not accurate anyway, the IDs are unique per asynchronous resource but not per asynchronous call.
Sorry, something went wrong.
There was a problem hiding this comment.
@addaleax, dropped the second sentence.
Sorry, something went wrong.
|
@nodejs/documentation (I'm feeling @vsemozhetbyt's absence these days. ❤️) |
Sorry, something went wrong.
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
fixes: #31661
Checklist