RFR: 8286378: Address possibly lossy conversions in java.base
Brian Burkhalter
bpb at openjdk.java.net
Tue May 10 22:57:49 UTC 2022
On Tue, 10 May 2022 21:32:10 GMT, Roger Riggs <rriggs at openjdk.org> wrote:
> PR#8599 8244681: proposes to add compiler warnings for possible lossy conversions
> From the CSR:
>
> "If the type of the right-hand operand of a compound assignment is not assignment compatible with the type of the variable, a cast is implied and possible lossy conversion may silently occur. While similar situations are resolved as compilation errors for primitive assignments, there are no similar rules defined for compound assignments."
>
> This PR anticipates the warnings and adds explicit casts to replace the implicit casts.
> In most cases, the cast matches the type of the right-hand side to type of the compound assignment.
> Since these casts are truncating the value, there might be a different refactoring that avoids the cast
> but a direct replacement was chosen here.
>
> (Advise and suggestions will inform similar updates to other OpenJDK modules).
IO, math, and NIO changes look fine.
-------------
Marked as reviewed by bpb (Reviewer).
PR: https://git.openjdk.java.net/jdk/pull/8642
More information about the security-dev
mailing list