-
Notifications
You must be signed in to change notification settings - Fork 44
Create flags and access levels abstraction #384
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
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Ladicek
reviewed
May 19, 2025
Ladicek
reviewed
May 19, 2025
Ladicek
reviewed
May 19, 2025
src/main/java/io/quarkus/gizmo2/impl/AbstractMethodCreatorImpl.java
Outdated
Show resolved
Hide resolved
Ladicek
reviewed
May 19, 2025
src/main/java/io/quarkus/gizmo2/impl/AnonymousClassCreatorImpl.java
Outdated
Show resolved
Hide resolved
Mostly LGTM, just a few small corrections and questions. |
Ladicek
reviewed
May 19, 2025
Ladicek
reviewed
May 19, 2025
Ladicek
reviewed
May 19, 2025
Fixes quarkusio#335. Version 1 of this change used type-safe constants for all of the modifiers and access levels; it was pretty nifty but added about 30-40 new types, so it seemed a bit to heavy to justify. This version makes a fair effort to put convenience methods in the right place, but otherwise does all checking at run time. At present, if you try to introduce a flag to a creator which always forces that flag to be set, then you will get an exception. I'm undecided whether this is a preferable behavior. I did not do anything about default access levels or modifiers yet, other than more or less mirroring what was already in the code.
…, so that we do not have the `NONE` location anymore
Ladicek
approved these changes
May 22, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #335.
Version 1 of this change used type-safe constants for all of the modifiers and access levels; it was pretty nifty but added about 30-40 new types, so it seemed a bit to heavy to justify.
This version makes a fair effort to put convenience methods in the right place, but otherwise does all checking at run time.
At present, if you try to introduce a flag to a creator which always forces that flag to be set, then you will get an exception. I'm undecided whether this is a preferable behavior.
I did not do anything about default access levels or modifiers yet, other than more or less mirroring what was already in the code.