Would be nice that C# compiler handled this case:

float f = 2.5;

I get the idea of protecting against precision loss. But why do you fail to compile for values that can be determined at compile time to not have precision loss?
It's no longer 2005, it's 2025 and changing this will only break the code that does not compile (like someones test suites might have such), which IMO is fine.

#programming #CSharp

I'm going to start mentoring my friend's son who just completed a coding boot camp through a local community college. I'm starting with #foss projects in languages/frameworks he was taught.ij the boot camp) #java #ReactJS

I maintain a #csharp project, but if anyone else has something that could use a potentially long term contributor I'll start working with him on issues. He needs to build his resume and learn to work with a distributed team.