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 ha
Wouter Swierstra wrote:
Test.IOSpecVersion 1.0
Shouldn't that be 0.1?
* Test.IOSpec.Teletype: a specification of getChar and putChar.
You use Dynamic for the data type in IORefs, this has the unfortunate
consequence of needing Typeable constraints. You could try to use
un
Hi,
Mostly for fun, and to see how well it would work, I made a
generalized/improved variant of the ReadP parser library.
Unlike ReadP ParseP can handle any type of token, and actually generates
error messages in case something goes wrong. It is also possible to use
things other then a list
unctions, since it is difficult
to determine what kind of encoding should be used given a Handle.
Homepage: http://twan.home.fmf.nl/compact-string/
Haddock: http://twan.home.fmf.nl/compact-string/doc/html/
Source:darcs get http://twan.home.fmf.nl/repos/compact-strin
John Meacham wrote:
I would highly highly recommend using utf8. inventing new formats
without very clear and pervasive benefits is just not good practice and
I wouldn't want to see it in standard libraries.
I still think it should not matter what the library uses *internally*.
The only way th
Chris Kuklewicz wrote:
Can I be among the first to ask that any Unicode variant of ByteString use a
recognized encoding?
In reading all the poke/peek function I did not see anything that your tag bits
accomplish that the tag bits in utf-8 do not, except that you want to write only
a single ro
releasing this in the hopes of getting
some feedback on the general idea.
Homepage: http://twan.home.fmf.nl/compact-string/
Haddock: http://twan.home.fmf.nl/compact-string/doc/html/
Source:darcs get http://twan.home.fmf.nl/repos/compact-string
Twan van Laarhoven
Is there any reason why IO should not be defined as:
> type IO a = ST RealWorld a
in implementations that support ST?
This way IORef/STRef and IOArray/STArray can be merged. I know under the
hood they already share code, but this way they can also share an interface.
Twan
I was wondering, in the MonadPlus documentation it says that:
* mzero is the identity of mplus (and some extra conditions)
* mplus is an associative operation
While for Monoid we have:
* mempty is identity of mappend
* mappend is an associative operation
MonadPlus is of course a 'stronger
