Why does the MSTest wizard the F suffix for doubles instead of D?

Question

When I create a test using MS Visual Studio's builtin unit test wizard it creates code with lines like the below:

double number = 0F;

In C# "F" stands for float, case-independent, and "D" for double. Using "F" suffix instead of "D" leads to precision lost.

If it's a bug, where can I report it to Microsoft?

Answer 1

I don't see how that could be anything but a bug. Completely harmless in this case, but still a bug. You can use Connect to report this kind of thing. However, I've had much more important bugs swept aside than this so I wouldn't expect much action.

HTH, Kent

Answer 2

If you use a Decimal (M suffix) then you don't have to worry about it having estimation errors or precision loss.

Answer 3

If the value is always 0F then no information will be lost at all.

In general any float can be converted to a double with no loss of precision (IEEE 754 assumed).

So long as the test value has not needed truncation to be represented as a float then there is no problem with regards to correctness. The confusion to end users and increased hassle when wanting to modify the values is still a problem.