Hi,
We've not encountered a concrete use-case for non-generic collections, although there could be an edge-case somewhere that uses them (e.g. a particular set of semantics associated with one association resulting in a specific collection class) - it certainly won't cause a major problem for us. On balance I'd vote for removing non-generic support if it helps maintainability. Pete From: [email protected] [mailto:[email protected]] On Behalf Of Oskar Berggren Sent: 07 September 2012 09:42 To: [email protected] Subject: [nhusers] RFC: Breaking changes for collections in NHibernate 4.0 Hi, The plan for NHibernate 4.0 is to support building it on .Net 4.0, including support for .Net's own ISet<T> instead of using Iesi.Collections. Today NHibernate 3.3 supports both non-generic and generic collections. For .Net's ISet<T>, there is no non-generic counterpart. Therefore, in NHibernate 4.0 support for non-generic ISet will be removed. Generic collections in general have been around since 2005, older than (almost?) all stable NHibernate versions. For the sake of consistency one could argue that support for the other non-generic collections should also be removed. Doing so would also reduce the amount of code somewhat. Is anyone still using the support for non-generic persistent collections in classes mapped with NHibernate? To such an extent that their removal would be a major problem? /Oskar -- You received this message because you are subscribed to the Google Groups "nhusers" 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/nhusers?hl=en. -- You received this message because you are subscribed to the Google Groups "nhusers" 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/nhusers?hl=en.
