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

Generated synthetic methods from ClassFactoryContextInterpreter should possibly throw relevant Errors? #1118

Open
msridhar opened this issue Aug 24, 2022 · 0 comments
Labels
low-priority A lower priority bug for WALA developers, but one for which we will happily accept a PR

Comments

@msridhar
Copy link
Member

Methods like Class.forName() can throw different types of Errors; see the Javadoc. Should we model these in the generated synthetic methods? It would be good for soundness, e.g., if you have a caller that catches an ExceptionInInitializerError. But probably this is a low-priority fix.

@msridhar msridhar added the low-priority A lower priority bug for WALA developers, but one for which we will happily accept a PR label Aug 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
low-priority A lower priority bug for WALA developers, but one for which we will happily accept a PR
Projects
None yet
Development

No branches or pull requests

1 participant