-
Notifications
You must be signed in to change notification settings - Fork 49k
[Flight] Clarify that location field is a FunctionLocation not a CallSite #33141
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
string, // function name | ||
string, // file name TODO: model nested eval locations as nested arrays | ||
number, // enclosing line number | ||
number, // enclosing column number |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Like it's not the enclosing of the function location but more like what enclosing means in the context of a callsite. I.e. function location.
Comparing: 4206fe4...fbd7352 Critical size changesIncludes critical production bundles, as well as any change greater than 2%:
Significant size changesIncludes any change greater than 0.2%: (No significant changes) |
FunctionDeclaration would also work. That might be confused with the AST nodes though. Separate name from "CallSite" definitely makes sen |
…Site (#33141) Follow up to #33136. This clarifies in the types where the conversion happens from a CallSite which we use to simulate getting the enclosing line/col to a FunctionLocation which doesn't represent a CallSite but actually just the function which only has an enclosing line/col. DiffTrain build for [a437c99](a437c99)
Follow up to #33136.
This clarifies in the types where the conversion happens from a CallSite which we use to simulate getting the enclosing line/col to a FunctionLocation which doesn't represent a CallSite but actually just the function which only has an enclosing line/col.