you don't want it to work.
Warnings are not something to be generally ignored. Only in very specific cases should you decide to ignore very specific warnings because you know they don't and can't pose a threat.
Things like @SuppressWarnings("unchecked") when casting a collection of JPA entities returned by a JPA method call to a generified collection of the expected return type.
Is the following supposed to work in java?
i = i++
Actually never mind because I don't care because that should never be in java code in the first place.
Your question seems similar since any code that has that in it would be wrong anyways - whether it works or not.
So the only correct answer would be to take it out so Eclipse can report the warnings and fix them so there aren't any.
Again, agreed. But sometimes we have to work with folks who don't agree, and one way to change opinions is to get facts and build a broad case. I'm trying to get the facts on this issue, despite it's being a bad practice.