The entry can be found here RSRP-273440
To sum it up it is about the warning that comparing a floating value with 0.0f should be changed to use a epsilon. This feature is fine because a 2 in float is maybee a 1.99999999999999999 and so the comparision can be false.
However for me and my colleagues the comparision with 0.0f which we use quite often does not need this check and produces to much noise...
The RSRP entry was closed as won't fix and I just want to talk about why it will not be changed for the comparision with 0.0f.
Is there a technical reason that the 0 is a 0.0000000000000000000000000000000000000000000001 or something like that?
I'm interested in reducing unnecessary warnings. If it is a valid conecern it is ok but I think it is not in the case for 0.