Comments

Charles wrote:

Agreed. I thought these CLR team videos would have invoked more conversation.

C

It's the redesigned site, I tell ya! You have seemingly discombobulated everybody...

Littleguru: No, that's not what I was suggesting, although with the minimal amount of explanation I did in the video, I can see how one would get that impression.

The primary problem is that there's no way to call this from a base class. If it weren't explicitly implemented, you could easily just do:

base.Dispose();

But because explicit implementations are emitted as private by the C# compiler (which the team firmly believes is the correct design), this isn't possible. You can't even do it in IL. One could imagine new C# syntax that made this possible:

((IDisposable)base).Dispose();

But this would only be possible with either
a) Explicitly implemented methods being emitted as family; or,
b) A "basecall" IL instruction.

We're going to look at these in future releases, but we dropped the idea for Whidbey.

Man, I didn't think I was a geek... But I even sound like one. Guess I should just go with the flow.

Fyi, a bit more reading on the whole disposable topic is available on my blog:
http://www.bluebytesoftware.com/blog/PermaLink.aspx?guid=1fe0f820-5b2b-4b17-82af-08142e7f308a

Feedback, questions, comments, etc. are welcome.