Let's just remove the old methods that take an object and replace them with the Type variant instead. I doubt many people are using IsAssignableFrom in its current form. So it's quite likely the breaking change will go mostly unnoticed.
Another reason to remove instead of deprecate is that there's actually a bit of potential ambiguity in having one overload take a parameter of Object and another take Type since Type is itself an Object but the behavior would be rather different. Votes? Jeff. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Yann Trevin Sent: Thursday, October 22, 2009 10:51 PM To: MbUnit.User Subject: MbUnit Re: Assert.IsAssignableFrom should have an override accepting two Type parameters. I propose that the methods taking an object argument be marked as "obsolete", or be simply removed (is it an acceptable breaking change?). Then we introduce a couple of overloads which take a Type argument instead. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "MbUnit.User" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/mbunituser?hl=en -~----------~----~----~----~------~----~------~--~---
