On 7 Apr 2009, at 07:37, David Menendez wrote:
On Mon, Apr 6, 2009 at 1:46 PM, Luke Palmer
wrote:
On Mon, Apr 6, 2009 at 11:42 AM, David Menendez
wrote:
Of course, this suggests that mfix should be fixM, so perhaps a
better
distinction is that mplus and mfix need to be defined per-mon
On Mon, Apr 6, 2009 at 1:46 PM, Luke Palmer wrote:
> On Mon, Apr 6, 2009 at 11:42 AM, David Menendez wrote:
>>
>> Of course, this suggests that mfix should be fixM, so perhaps a better
>> distinction is that mplus and mfix need to be defined per-monad,
>> whereas filterM and replicateM are generi
On Mon, Apr 6, 2009 at 11:42 AM, David Menendez wrote:
> Of course, this suggests that mfix should be fixM, so perhaps a better
> distinction is that mplus and mfix need to be defined per-monad,
> whereas filterM and replicateM are generic.
Don't you think that is an incidental distinction, not
On Mon, Apr 6, 2009 at 10:02 AM, Sjoerd Visscher wrote:
> Considering these naming conventions:
> http://haskell.org/ghc/docs/latest/html/libraries/base/Control-Monad.html#3
>
> • A postfix 'M' always stands for a function in the Kleisli category: The
> monad type constructor m is added to functio
Considering these naming conventions:
http://haskell.org/ghc/docs/latest/html/libraries/base/Control-Monad.html#3
• A postfix 'M' always stands for a function in the Kleisli category:
The monad type constructor m is added to function results (modulo
currying) and nowhere else. So, for example
