On Tue, Aug 24, 2010 at 05:12, John Lato wrote:
> Oleg included the error state to enable short-circuiting of computation, and
> I guess everyone just left it in. Recently I've been wondering if it should
> be removed, though, in favor requiring explicit (i.e. explicit in the type
> sig) exceptio
On Tue, Aug 24, 2010 at 7:16 PM, Gregory Collins wrote:
> John Lato writes:
>
> > Oleg included the error state to enable short-circuiting of
> > computation, and I guess everyone just left it in. Recently I've been
> > wondering if it should be removed, though, in favor requiring explicit
> > (
John Lato writes:
> Oleg included the error state to enable short-circuiting of
> computation, and I guess everyone just left it in. Recently I've been
> wondering if it should be removed, though, in favor requiring explicit
> (i.e. explicit in the type sig) exceptions for everything. I'm not
>
>
> From: Magnus Therning
>
> On 24/08/10 03:47, John Millikin wrote:
> [...]
> > I would like to avoid hard-coding the error type to SomeException,
> because
> > it forces libraries to use unsafe/unportable language features (dynamic
> > typing and casting). However, given the apparent practical
On Fri, Aug 20, 2010 at 21:02, Paulo Tanimoto wrote:
> Hi John,
>
> What do you think of putting those parsing functions like head, last,
> length, etc, under another module or, alternatively, putting the main
> definitions under another module (say, Base or Core)? I wouldn't mind
> if they all g
On Sat, Aug 21, 2010 at 12:30 AM, John Millikin wrote:
> Just released 0.2. It has the text IO and codecs module, with support
> for ASCII, ISO-8859-1, UTF-8, UTF-16, and UTF-32. It should be
> relatively easy to add support for codec libraries like libicu or
> libiconv in the future. Both encodin
Hi John,
What do you think of putting those parsing functions like head, last,
length, etc, under another module or, alternatively, putting the main
definitions under another module (say, Base or Core)? I wouldn't mind
if they all get re-exported.
I say that because since the library aims to be
Just released 0.2. It has the text IO and codecs module, with support
for ASCII, ISO-8859-1, UTF-8, UTF-16, and UTF-32. It should be
relatively easy to add support for codec libraries like libicu or
libiconv in the future. Both encoding and decoding are incremental, so
you can (for example) process
Just released version 0.1.1, which includes:
* Michael Snoyman's improved 'consume'
* (>==>) and (<==<) operators, for composing enumerators (sort of like
(>=>) for monads)
* ($$) operator, an alias for (==<<), which matches Oleg's operator
and makes reading 'run' statements a bit easier.
* catchE
