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

Store output of @wrapmodule #398

Open
sloede opened this issue Jan 5, 2024 · 2 comments
Open

Store output of @wrapmodule #398

sloede opened this issue Jan 5, 2024 · 2 comments

Comments

@sloede
Copy link
Contributor

sloede commented Jan 5, 2024

Is it possible to get a nice textual representation of the code generated by @wrapmodule? My use case is that I'd like to be able to see how types and wrapped functions are actually constructed and possibly add docstrings to them that point to actual code (instead of attaching docstrings only to symbol name).

@sloede
Copy link
Contributor Author

sloede commented Feb 13, 2024

@barche Do you see a way that this could be achieved? I am also wondering if storing the output might help with precompilation.

@barche
Copy link
Collaborator

barche commented Feb 13, 2024

This would be interesting to have, most of the generated code is in the output of build_function_expression, which gets called for each wrapped function. It's pretty ugly in its bare form, but maybe there are already some Julia metaprogramming tools that can help in making it readable and then store it somewhere.

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

2 participants