Had a coworker ask me this, and in my brain befuddled state I didn't have an answer:
Why is it that you can do:
string ham = "ham " + 4;
But not:
string ham = 4;
If there's an implicit cast/operation for string conversion when you are concatenating, why not the same when assigning it as a string? (Without doing some operator overloading, of course)
Reference
Reference
The expression
Forces an implicit conversion of 4 to a string based on the combination of a string type and the addition operator. Specifically it's a quality of the "+" operator, and when doing operator overloading you can manually implement the same type of thing.
A similar and less obvious example would be:
long myNumber = Int64.MaxValue - 1;
In this case "1" should be evaluated as a 32-bit integer but it is implicitly converted. You can check the C# language spec section 6.1 for an exhaustive list of implicit conversions supported by the compiler.
edit: to be clear, the language spec section i referred to lists implicit conversions supported by the compiler, while operators like "+" can have their own supported conversions.
The value of the righthand side of the first expression is a string, while the value of the righthand side of the second expression is not. The concatonation is providing the magic in the first scenario, where the assignment isn't doing anything special. In the second scenario, the assignment continues to play dumb.
There is no implicit conversion when doing concatenation. String concatenation resolves down to a String.Concat call, which has an overload which takes Objects. It is this overload which performs an (explicit) conversion to string.
When concatenating the compiler turns the statement
"ham" + 4
into a call toString.Concat
, which takes twoobject
parameters, so the value4
is boxed and thenToString
is called on that.For the assignment there is no implicit conversion from
int
tostring
, and thus you cannot assign4
to astring
without explicitly converting it.In other words the two assignments are handled very differently by the compiler, despite the fact that they look very similar in C#.