Community
Participate
Working Groups
Putting this good idea lifted from Cedric Beusts blog into bugzilla so it doesnt get lost: "Autoboxing I have stayed away from autoboxing so far, probably because I have a vague feeling of losing control of the performance of my code. I don't think it is justified, though, so autoboxing can come in handy and make your code a little bit more readable. I think I would encourage developers to flag their code when such autoboxing is happening, and I am pretty sure that IDE's will soon be able to do the same."
This is something we had in mind, like we do optionally warn when performing innerclass access emulation. Another one would be to warn when inserting generic cast (implicitly during compile).
*** Bug 80457 has been marked as a duplicate of this bug. ***
*** Bug 68269 has been marked as a duplicate of this bug. ***
Added optional compiler diagnosis when boxing/unboxing conversion is performed. Corresponding problem IDs are: IProblem.BoxingConversion and IProblem.UnboxingConversion. * COMPILER / Reporting Boxing/Unboxing Conversion * When enabled, the compiler will issue an error or a warning whenever a boxing or an unboxing * conversion is performed. * - option id: "org.eclipse.jdt.core.compiler.problem.autoboxing" * - possible values: { "error", "warning", "ignore" } * - default: "ignore"
Fixed
Verified in I20050214