Sorry -- yes, you are correct. In my haste to reply, I conflated the two :) Usually discussions about IESI collections tend to center around ISet<T> and so in my quick read I assumed that's what this was about as well!
Regards, Steve Bohlen [email protected] http://blog.unhandled-exceptions.com http://twitter.com/sbohlen On Sun, Jul 24, 2011 at 11:20 AM, Nathan Brown <[email protected]> wrote: > HashSet<T> is in .NET 3.5. ISet<T> isn't introduced until .NET 4.0. > There are a number of places that already use > System.Collections.Generic.HashSet<T>. It looks like they are used > for the ability to do Union. > > On Jul 24, 5:22 am, Stephen Bohlen <[email protected]> wrote: > > Isn't it the case that since we're not ready (yet) to state a hard dep. > on > > .NET 4.0, internally you need to rely upon the IESI collections impl. > > of hashset? > > > > Steve Bohlen > > [email protected]http://blog.unhandled-exceptions.comhttp:// > twitter.com/sbohlen > > > > > > > > > > > > > > > > On Sat, Jul 23, 2011 at 8:42 PM, Nathan Brown <[email protected]> wrote: > > > I was talking about code in the NHibernate code base. I've been > > > working on improving the SQL formatter. I ended up using the > > > System.Collections.Generic.HashSet. > > > > > On Jul 22, 6:04 am, Fabio Maulo <[email protected]> wrote: > > > > You can use ISet (NET4) and the CollectionTypeFactory for it > (available > > > in > > > > nuget) > > > > > > On Thu, Jul 21, 2011 at 4:50 PM, Nathan Brown <[email protected]> > wrote: > > > > > Both types of sets are used in the NHibernate code base. I was > > > > > wondering what the future direction of this is going to be? Which > > > > > should be used for new development? > > > > > > > Thanks > > > > > > -- > > > > Fabio Maulo >
