On Tue, Aug 26, 2008 at 11:11 AM, Neil Mitchell
2- Data.Set is not obviously the best underlying implementation (in fact it is obviously not the best underlying implementation, this and Data.Map etc really should be pensioned off to hackage along with the rest of the badly documented, unreliable, inefficient and unstable junk :-)
Data.Set is an interface, which you seem to think is not the fastest implementation of that interface. If you can expose the same interface, but improve the performance, and demonstrate that the performance is better, then go for it! I'd support such a library change proposal.
The problem with Data.Set and other collection types is that they're *not* defined as interfaces. If Data.Set was defined using a type class and maybe some associated data types it would be easier to provide an alternative implementation. Cheers, Johan