-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
fix(#16610): warn ignored Scaladoc on multiple enum cases #19555
fix(#16610): warn ignored Scaladoc on multiple enum cases #19555
Conversation
Before this commit, the compiler ignored Scaladoc comment on multiple enum cases without warning. This is partly expected because the case to which the doc is attached is ambiguous, but we should at least warn users that the comment is ignored by compiler due to ambiguity and they should take an action if they want the doc to be displayed.
5c252cb
to
76ee412
Compare
…on-enum-cases-without-warn
@Florian3k would you be kind enough to review the changes? |
Hi, sorry for the delay, I've somehow missed the notification. I'll get to this ASAP. |
This looks good, but to add new warning without flag we need to wait for 3.5.0. |
I haven't tried yet, so I'm not sure, but may I try it? |
|
…on-enum-cases-without-warn
> to add new warning without flag we need to wait for 3.5.0. See scala#19555 (comment)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
close #16610 Before this commit, the compiler ignored Scaladoc comment on multiple enum cases without warning. This is partly expected because the case to which the doc is attached is ambiguous, but we should at least warn users that the comment is ignored by compiler due to ambiguity and they should take an action if they want the doc to be displayed. [Cherry-picked 11a6f0a][modified]
close #16610
Before this commit, the compiler ignored Scaladoc comment on multiple enum cases without warning.
This is partly expected because the case to which the doc is attached is ambiguous, but we should at least warn users that the comment is ignored by compiler due to ambiguity and they should take an action if they want the doc to be displayed.