Creepy Implicitness
Posted in Development
Generally, I’m not against implicit operators, but this LINQ/XML syntax gives me creeps:
new XAttribute (XNamespace.Xmlns + "foo", "bar")
Took me a while to understand that XNamespace has an implicit operator which allows this string “concatenation.”
Patrik
on January 23, 2008
I think the rule of thumb for using implicit operators is that they're fine as long as you don't lose any information when doing the cast, in other words as long as the object you end up with can be used to create a new object of the original type and they're considered equal.
So I'd say that this is a mighty fine example of the implicit operator when used at it's best.