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.

Sign up for GitHub

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

Jump to bottom

Replace @Optional with @OptArg or similar #19

Open
DarkArc opened this issue Dec 22, 2015 · 1 comment
Open

Replace @Optional with @OptArg or similar #19

DarkArc opened this issue Dec 22, 2015 · 1 comment

Comments

@DarkArc
Copy link
Member

DarkArc commented Dec 22, 2015

Currently if using the @Optional annotation to specify an optional argument, within a class file also using the JDK Optional class, or the Guava Optional class you're forced to use the expanded type name so as to specify which Optional you're referring to.

To resolve this naming conflict, I suggest making the @Optional annotation an @OptArg annotation or similar.
@elysweyr
Copy link

What about this issure? It's still open: what'll happen?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@DarkArc @elysweyr