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

Using @Arg alone causes RuntimeException #16

Open
tom91136 opened this issue Nov 18, 2015 · 1 comment
Open

Using @Arg alone causes RuntimeException #16

tom91136 opened this issue Nov 18, 2015 · 1 comment
Labels

Comments

@tom91136
Copy link
Owner

Using @Arg alone with a call to Akatsuki.restore and a non-null instance state causes Akatsuki to look for the @Retained's retainer class which does not exist.

@tom91136
Copy link
Owner Author

This has to be implemented in the generated code(a.k.a compile time) otherwise an annotation query has to be done to distinguish which annotation type is actually being used. Android seems to have questionable performance when it comes to runtime annotation queries so this fix ill be implemented via CLASS_LUT and a runtime fall-back in case the LUT option is turned off

@tom91136 tom91136 added the bug label Nov 21, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant