I love the internet

[andrewducker]

Having, during discussion with simont and call_waiting in my previous post about c# method overload resolution, reached a reasonably good understanding of what the compiler was doing, I did what any sensible person would do. Something you couldn't easily do 20 years ago. I emailed one of the compiler writers, Eric Lippert, and asked him why it worked that way.

And he emailed me back saying, yes, it was a deliberate decision. And here was his blog post from 2007 explaining it.

Now that's service!

Comments

[call-waiting.livejournal.com]

Ah! Now that makes a lot of sense. Hm. I'm sure there's probably a different way around the problem than fritzing with the method resolution rules, though. It seems rather heavy-handed.