We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Generated functions(EDIT: in GG) encode the programs into types, in this way the world age problem got solved.
However, the encoded types finally become too large and crash the compiler: #46
An alternative solution is reducing the encoded types but keeping the information.
So far no idea of this approach but just now chatting with some one inspired me and I now thought this deserves some research.
A straightforwaed idea is constructing a bi mapping from a Julia AST to a flatten byte sequence, and the latter can be used as a value type.
The text was updated successfully, but these errors were encountered:
If this works, #46 can get resolved.
Sorry, something went wrong.
ast compressing for function body: #47, #45
bb0b9b7
Revert "ast compressing for function body: JuliaStaging#47, JuliaStag…
63bd98c
…ing#45" This reverts commit bb0b9b7.
Revert "ast compressing for function body: #47, #45"
8c0ca83
This reverts commit bb0b9b7.
No branches or pull requests
Generated functions(EDIT: in GG) encode the programs into types, in this way the world age problem got solved.
However, the encoded types finally become too large and crash the compiler: #46
An alternative solution is reducing the encoded types but keeping the information.
So far no idea of this approach but just now chatting with some one inspired me and I now thought this deserves some research.
A straightforwaed idea is constructing a bi mapping from a Julia AST to a flatten byte sequence, and the latter can be used as a value type.
The text was updated successfully, but these errors were encountered: