Hi Michael
If you going to the trouble of constructing a sum type (obliged to be
2 parameter) expressly to play well with the favourite single
parameter classes e.g. Functor/ Applicative / Monad [*], maybe it is
worth considering new names for the type and its constructors relating
to what the
On Tue, Jun 29, 2010 at 10:18 AM, Stephen Tetley
stephen.tet...@gmail.comwrote:
Hi Michael
If you going to the trouble of constructing a sum type (obliged to be
2 parameter) expressly to play well with the favourite single
parameter classes e.g. Functor/ Applicative / Monad [*], maybe it is
Hi Michael
Good names are a problem of course.
The Applicative Programming with Effects Paper has the monodial
accumulating applicative instance on a sum type Conor McBride and
Ross Paterson call Except:
data Except err a = OK a | Failed err
The names are nice and to the point, but they would
On Jun 29, 2010, at 6:02 AM, Stephen Tetley wrote:
Hi Michael
Good names are a problem of course.
The Applicative Programming with Effects Paper has the monodial
accumulating applicative instance on a sum type Conor McBride and
Ross Paterson call Except:
data Except err a = OK a | Failed err
On Tue, Jun 29, 2010 at 02:56:18PM -0500, Jeremy Shaw wrote:
On Jun 29, 2010, at 6:02 AM, Stephen Tetley wrote:
The Applicative Programming with Effects Paper has the monodial
accumulating applicative instance on a sum type Conor McBride and
Ross Paterson call Except:
data Except err a = OK
Hi all,
I'll admit, the original idea for this package was something to place in
ACME ;). However, it's goal is to solve a real problem: the lack of good
instances on the Either type. As a brief summary, Either has no Applicative
or Monad instances in the base library, has 2 reasonable
It looks like good work, but I would be hesitent about depending on a
package which pulled in both mtl and tranformers.
Maybe that's just superstition - I haven't tried it.
Antoine
On Jun 28, 2010 5:51 PM, Michael Snoyman mich...@snoyman.com wrote:
Hi all,
I'll admit, the original idea for
As far as I know, the only issue with depending on both is the conflicting
orphan Monad instance for Either. Can anyone either confirm or deny this?
On Tue, Jun 29, 2010 at 5:11 AM, Antoine Latter aslat...@gmail.com wrote:
It looks like good work, but I would be hesitent about depending on a
On 29 June 2010 15:20, Michael Snoyman mich...@snoyman.com wrote:
As far as I know, the only issue with depending on both is the conflicting
orphan Monad instance for Either. Can anyone either confirm or deny this?
Since you're being naughty and using package-qualified imports, it
should be OK
On Tue, Jun 29, 2010 at 8:24 AM, Ivan Miljenovic
ivan.miljeno...@gmail.comwrote:
On 29 June 2010 15:20, Michael Snoyman mich...@snoyman.com wrote:
As far as I know, the only issue with depending on both is the
conflicting
orphan Monad instance for Either. Can anyone either confirm or deny
On 29 June 2010 15:38, Michael Snoyman mich...@snoyman.com wrote:
On Tue, Jun 29, 2010 at 8:24 AM, Ivan Miljenovic ivan.miljeno...@gmail.com
wrote:
On 29 June 2010 15:20, Michael Snoyman mich...@snoyman.com wrote:
As far as I know, the only issue with depending on both is the
conflicting
11 matches
Mail list logo
