Inconsistent derivation for generic collections

P

Peter Duniho

Dilip said:
That much is certainly true. I guess my objective was to just inform
you that I did converse with a few Microsoft folks and they did admit
that for Michi's particular use-case, the way ICollection and friends
are designed today, solutions _are_ a bit awkward.

And I agree with that. I just don't agree that the awkwardness is
gratuitous or that it renders the classes useless.
Thats not to say a
workaround is impossible, I am just saying there is no straightforward
way to do it when other languages seem to not suffer from this
problem.

I guess that depends on your definition of "straightforward". It's
certainly a matter of opinion, and I think the workarounds I've offered
here are pretty straightforward (including the suggestion to just write
the overloads and be done with it).

Others may disagree, and I have no problem with that. It's the more
general impugning of the .NET Framework that I find annoying, especially
when it implies that everyone should share those feelings of discontentment.

Pete
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top