query: Why is 'f' required on floats in C#
positive_passages.docid: 17720
positive_passages.text: Why is the "f" required when declaring floats?
negative_passages.docid: 116238
negative_passages.text: Set decimal separator when using f:convertNumber
negative_passages.docid: 70844
negative_passages.text: Conflict between endfloat and figure floats included via macro
negative_passages.docid: 10823
negative_passages.text: Is floating point arbitrary precision available?
negative_passages.docid: 33934
negative_passages.text: understanding floating point variables
negative_passages.docid: 37139
negative_passages.text: Workaround for lack of 'nameof' operator in C# for type-safe databinding?
negative_passages.docid: 115180
negative_passages.text: Difference between [h] and [H] in float position
negative_passages.docid: 12879
negative_passages.text: How dangerous is it to compare floating point values?
negative_passages.docid: 65822
negative_passages.text: FirstOrDefault In F#
negative_passages.docid: 35622
negative_passages.text: Is floating-point == ever OK?
negative_passages.docid: 131653
negative_passages.text: Confused with F# List.nth's argument order
negative_passages.docid: 99281
negative_passages.text: Explain the ' notation in F#
negative_passages.docid: 68812
negative_passages.text: What does the '=>' syntax in C# mean?
negative_passages.docid: 31978
negative_passages.text: Why doesn't C have unsigned floats?
negative_passages.docid: 132871
negative_passages.text: C# Float expression: strange behavior when casting the result float to int
negative_passages.docid: 7533
negative_passages.text: Why do floating-point numbers have signed zeros?
negative_passages.docid: 142998
negative_passages.text: No overflow exception for int in C#?