-
Notifications
You must be signed in to change notification settings - Fork 119
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
We probably don't handle recent Java features #303
Comments
I think Since the treatment of most node types is quite formulaic, I think we might be able to replace this with a |
This is much more robust than overriding individual visitor methods. It means we won't forget to check some property of an AST node, and it also means we automatically handle new kinds of nodes. Using reflection does make this potentially more expensive than having individual visitor methods. The overhead is likely to be small compared to the cost of compiling source code to produce the ASTs in the first place. Fixes #303. RELNOTES=n/a PiperOrigin-RevId: 492735035
This is much more robust than overriding individual visitor methods. It means we won't forget to check some property of an AST node, and it also means we automatically handle new kinds of nodes. Using reflection does make this potentially more expensive than having individual visitor methods. The overhead is likely to be small compared to the cost of compiling source code to produce the ASTs in the first place. Fixes #303. RELNOTES=n/a PiperOrigin-RevId: 492735035
This is much more robust than overriding individual visitor methods. It means we won't forget to check some property of an AST node, and it also means we automatically handle new kinds of nodes. Using reflection does make this potentially more expensive than having individual visitor methods. The overhead is likely to be small compared to the cost of compiling source code to produce the ASTs in the first place. Fixes #303. RELNOTES=n/a PiperOrigin-RevId: 492735035
This is much more robust than overriding individual visitor methods. It means we won't forget to check some property of an AST node, and it also means we automatically handle new kinds of nodes. Using reflection does make this potentially more expensive than having individual visitor methods. The overhead is likely to be small compared to the cost of compiling source code to produce the ASTs in the first place. Fixes #303. RELNOTES=n/a PiperOrigin-RevId: 492735035
This is much more robust than overriding individual visitor methods. It means we won't forget to check some property of an AST node, and it also means we automatically handle new kinds of nodes. Using reflection does make this potentially more expensive than having individual visitor methods. The overhead is likely to be small compared to the cost of compiling source code to produce the ASTs in the first place. Fixes #303. RELNOTES=n/a PiperOrigin-RevId: 492735035
This is much more robust than overriding individual visitor methods. It means we won't forget to check some property of an AST node, and it also means we automatically handle new kinds of nodes. Using reflection does make this potentially more expensive than having individual visitor methods. The overhead is likely to be small compared to the cost of compiling source code to produce the ASTs in the first place. Fixes #303. RELNOTES=n/a PiperOrigin-RevId: 492735035
This is much more robust than overriding individual visitor methods. It means we won't forget to check some property of an AST node, and it also means we automatically handle new kinds of nodes. Using reflection does make this potentially more expensive than having individual visitor methods. The overhead is likely to be small compared to the cost of compiling source code to produce the ASTs in the first place. Fixes #303. PiperOrigin-RevId: 492735035
Given that cb6486c only recently added support for try-with-resources, I'd assume that we aren't yet handling
instanceof String s
or switch expressions + yield, much less any preview features. (I pulled this list from the Java 17TreeVisitor
API.)The text was updated successfully, but these errors were encountered: