ANNOUNCE: multiset 0.1
Hello, I have just uploaded version 0.1 of the multiset library to hackage. This package provides Data.MultiSet and Data.IntMultiSet modules. A multiset or bag is like a set, but it can contain multiple copies of the same element. The library is already pretty much finished, maybe I should have called it 1.0. It implements the same interface as Data.Set, with some additional functions specific to multisets. Hackage: http://hackage.haskell.org/cgi-bin/hackage-scripts/package/multiset-0.1 Haddock: http://twan.home.fmf.nl/multiset/doc/ Darcs: http://twan.home.fmf.nl/repos/multiset/ Twan
Hackage: http://hackage.haskell.org/cgi-bin/hackage-scripts/package/multiset-0.1 Haddock: http://twan.home.fmf.nl/multiset/doc/ Darcs: http://twan.home.fmf.nl/repos/multiset/
Seeing all these nice little packages (i.e. also bimap), is there a cute way to get a binary distribution - similar to the current extra libs - with many packages already included, so that installation can be accomplished in one go (maybe for the next ghc release)? Cheers Christian
Am Donnerstag, 7. Februar 2008 02:43 schrieb Twan van Laarhoven:
Hello,
I have just uploaded version 0.1 of the multiset library to hackage. This package provides Data.MultiSet and Data.IntMultiSet modules. A multiset or bag is like a set, but it can contain multiple copies of the same element.
The library is already pretty much finished, maybe I should have called it 1.0. It implements the same interface as Data.Set, with some additional functions specific to multisets.
Hackage: http://hackage.haskell.org/cgi-bin/hackage-scripts/package/multiset-0.1 Haddock: http://twan.home.fmf.nl/multiset/doc/ Darcs: http://twan.home.fmf.nl/repos/multiset/
Twan
Hello, this is interesting. A few days ago I discovered that I needed such a library and decided to implement it myself. However, I had not started yet when I received your e-mail. A bit of criticism concerning the name: According to the English Wikipedia, multiset is a single word. So the identifiers should be Multiset and IntMultiset instead of MultiSet and IntMultiSet. However, I think it would be even better to just use Bag and IntBag as identifiers. Those are shorter and maybe easier to remember. After all, the term bag is fairly standard. I think that actually your multiset/bag implementation should be a part of the containers package. So why not ask the maintainers of the containers package for permission to add your implementation and change the identifiers to Bag and IntBag during this process? This would be great. Best wishes, Wolfgang
-----Original Message----- From: haskell-bounces@haskell.org [mailto:haskell-bounces@haskell.org] On Behalf Of Wolfgang Jeltsch Sent: Thursday, February 07, 2008 11:08 AM To: haskell@haskell.org Subject: Re: [Haskell] ANNOUNCE: multiset 0.1
Am Donnerstag, 7. Februar 2008 02:43 schrieb Twan van Laarhoven:
Hello,
I have just uploaded version 0.1 of the multiset library to hackage. This package provides Data.MultiSet and Data.IntMultiSet modules. A multiset or bag is like a set, but it can contain multiple copies of the same element.
The library is already pretty much finished, maybe I should have called it 1.0. It implements the same interface as Data.Set, with some additional functions specific to multisets.
Hackage:
http://hackage.haskell.org/cgi-bin/hackage-scripts/package/mul tiset-0.1
Haddock: http://twan.home.fmf.nl/multiset/doc/ Darcs: http://twan.home.fmf.nl/repos/multiset/
Twan
Hello,
this is interesting. A few days ago I discovered that I needed such a library and decided to implement it myself. However, I had not started yet when I received your e-mail.
A bit of criticism concerning the name: According to the English Wikipedia, multiset is a single word. So the identifiers should be Multiset and IntMultiset instead of MultiSet and IntMultiSet. However, I think it would be even better to just use Bag and IntBag as identifiers. Those are shorter and maybe easier to remember. After all, the term bag is fairly standard.
For users of C++ STL, Multiset is probably easier to remember. Greetings, Sebastian Setzer
I think that actually your multiset/bag implementation should be a part of the containers package. So why not ask the maintainers of the containers package for permission to add your implementation and change the identifiers to Bag and IntBag during this process? This would be great.
Best wishes, Wolfgang _______________________________________________ Haskell mailing list Haskell@haskell.org http://www.haskell.org/mailman/listinfo/haskell
Sebastian Setzer wrote on Thursday, 7 February, 2008 11:14:
Am Donnerstag, 7. Februar 2008 02:43 schrieb Twan van Laarhoven:
A bit of criticism concerning the name: According to the English Wikipedia, multiset is a single word. So the identifiers should be Multiset and IntMultiset instead of MultiSet and IntMultiSet. However, I think it would be even better to just use Bag and IntBag as identifiers. Those are shorter and maybe easier to remember. After all, the term bag is fairly standard.
For users of C++ STL, Multiset is probably easier to remember.
Off-topic: For further discussion of bag terminology, see EWD786a (http://www.cs.utexas.edu/~EWD/ewd07xx/EWD786a.PDF, transcript at http://www.cs.utexas.edu/~EWD/transcriptions/EWD07xx/EWD786a.html). Groetjes, <>< Marnix -- Marnix Klooster | Software Engineer, ERP LN Enterprise Server | Infor | (+31 or 0)342-428511 | marnix.klooster@infor.com | Infor Global Solutions (Barneveld) BV | P.O. box 143 | 3770 AC Barneveld | The Netherlands
That would make for a nice script font :) Oh, wait, there is one already: http://lucacardelli.name/Fonts.htm
participants (6)
-
Christian Maeder -
Marnix Klooster -
Setzer, Sebastian (ext) -
Thomas Schilling -
Twan van Laarhoven -
Wolfgang Jeltsch