-
Notifications
You must be signed in to change notification settings - Fork 52
Add docs for isprecompilable
#416
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
This also enhances its implementation to make it more flexible. Closes #411
| If `mi` has been compiled by the time its defining module "closes" (the final | ||
| `end` of the module definition) and `isprecompilable(mi)` returns `true`, then |
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.
If
mihas been compiled by the time its defining module "closes" (the final
endof the module definition)
When might this happen? Would it mean that the defining module would need to call mi?
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.
If mi corresponds to f(x), then just calling f(x) before the module closes will do it. For the inferrable callees of this method, it won't matter if it's inside or outside a @compile_workload block. For any runtime-dispatched ones, it will matter a lot. But if you're thinking about a single "flame" on the flamegraph, that's irrelevant, because one flame = the inferrable callees of the entrypoint (base of the flame).
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.
I posted a few comments / suggestions, but overall looks good, thank you!
Co-authored-by: Charles Kawczynski <kawczynski.charles@gmail.com>
This also enhances its implementation to make it more flexible.
Closes #411