3 ms·
So it's not actually the type inference that's the problem -- it's developers who carelessly define implicit conversion operators on their classes.
by profquail 12y ago
So it's not actually the type inference that's the problem -- it's developers who carelessly define implicit conversion operators on their classes.
- JoeAltmaier 12y agoStrings have built-in conversion, right?
- nanofortnight 12y agoThe only built-in implicit conversions in C# are for numerics, and there isn't a loss in precision for those (with the exception of int/uint/long/ulong -> float and long/ulong -> double, where there is a loss of precision). http://msdn.microsoft.com/en-us/library/y5b434w4.aspx http://msdn.microsoft.com/en-us/library/y5b434w4.aspx int i = "5"; would not work.
- recursive 12y agoNot the kind you seem to be thinking of.