Community
Participate
Working Groups
Consider an Enum class having non-deprecated as well as deprecated constants: enum E { A, B, @Deprecated C } Assuming that you want to have zero warnings in the project, it's not pssible to set that "Incomplete 'switch' cases on enum" should cause warning. This causes warning about missing case (expected): E e = ....; switch (e) { case A: case B: } But adding the required 'case C' triggers deprecation warning. In my opinion, the deprecation should be marked in the code as usual (strike-through by default), but since it's required for switch completeness, it should not trigger warning.
Thanks for taking a look.
I'd like to fix all deprecation warnings in my code and configure deprecation to be an error. This is a blocker for this endeavor.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
This fell through the cracks. Completely suppressing this warning doesn't sound good to me, since in otherwise warning-free code this case block will be practically dead code, that should be flagged. OTOH a new option just for this use cases appears to be overkill. I'm putting the bug back into the common bucket to give others a chance to chime in.
