-
-
Notifications
You must be signed in to change notification settings - Fork 9
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
Split errors into AllocationSite
, AllocatingRuntimeCall
, and DynamicDispatch
#36
Conversation
d89054a
to
690ede9
Compare
Should we call them errors or something else? And maybe we should add an option to the macro so it executes anyway? But prints this as a warning? |
Open to suggestions 🙂
I'd be open to a |
I guess errors are fine. They look like errors, so I guess that sets the expectation |
…amicDispatch` This makes it much easier to understand the three main enemies one will have when trying to eliminate allocations. This also does a major re-factoring of the `allocfunc.jl` internals while we're at it.
Try and look through the global to see it's initializer
This needs to be expanded still, but it's much better than nothing. This also bundles up various tweaks to the first commit in this PR.
Still needs a bit of refinement/DRY, but this is enough to get things working.
Apparently terminal support for this is quite poor, so perhaps we should avoid it all together?
cf5f78f
to
644bb5f
Compare
Time to go public 😎 |
This makes it much easier to understand the three main opponents one will have when trying to eliminate allocations.
This also does a major re-factoring of the
allocfunc.jl
internals while we're at it.Example: