Skip to content
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

design of @check_allocs for static compilation #63

Open
JeffBezanson opened this issue Nov 29, 2023 · 0 comments
Open

design of @check_allocs for static compilation #63

JeffBezanson opened this issue Nov 29, 2023 · 0 comments

Comments

@JeffBezanson
Copy link
Member

The way @check_allocs currently works is unintuitive, since it is a static analysis but requires you to actually call the function. Of course we need that to pick up actual argument types, and it works ok for running tests, but we will need something that is compatible with a static compilation workflow. For example, a macro that records the method in a list somewhere, and then if you compile the code with PackageCompiler or StaticCompiler it calls check_allocs on all specializations to report errors before generating the output. We can use this issue to hash out exactly how it should work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant