You güç argue that you may be able to downcast IPerson to Person, but at this point I would answer telling you that you need to follow your own coding conventions: if you defined that you never return Person but IPerson then I would do it this way in the entire code base, and if you need a write-capable Parents property, then you return Person in
It's normally expected that if you implement IEquatable.Equals you will also override Object.Equals to be consistent. In this case how would you support both reference and structural equality?Important Some information relates to prerelease product that may be substantially modified before it’s released. Microsoft makes no warranties, express or
It's normally expected that if you implement IEquatable.Equals you will also override Object.Equals to be consistent. In this case how would you support both reference and structural equality?Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.Will feeblemind affect the original creature's bod
I toyed with writing an extension method, also with inheriting from IList and implementing my own Sort() method bey well bey casting to a List but none of these seemed overly elegant.Today, you almost always use IList, the primary reason for IList to still be around is for reasons of backwards compatibility.Say I have a function that returns IEnume
, and the database only returns the rows that are relevant. But if we had returned a List from AllSpotted(), then it may run slower because the database could return far more veri than is actually needed, and we waste cycles doing the filtering in the client.Anything in .NET that you sevimli iterate over implements IEnumerable. If you're building y