It isn't. But a lot of people are using it, and I am going to do my best to avoid breaking backcomp at a whim. Breaking it to its own project means that we are free not to think about it and have a fresh new start.
Mostly, though, I am not sure if we even want to have a common repository. On Wed, Nov 12, 2008 at 6:16 PM, Nathan Stott <[EMAIL PROTECTED]> wrote: > Currently in my projects, I've been making my own IRepository that has many > less methods and then implementing my IRepository with Rhinos. > I am definitely in favor of anything that simplifies the Rhino IRepository > interface. > > I don't understand how moving IRepository<T> to its own project is going to > simplify the interface, though. > > > On Wed, Nov 12, 2008 at 10:13 AM, Ayende Rahien <[EMAIL PROTECTED]> wrote: > >> For a long time, IRepository<T> has been bothering me.In particular, we >> have literally scores of methods there, and the interface is way too big and >> complex. >> >> My current action is to move the IRepository<T> and associates to their >> own project, thoughts? >> >> >> > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" 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/rhino-tools-dev?hl=en -~----------~----~----~----~------~----~------~--~---
