On 12-09-30 06:33 PM, Jake McArthur wrote:
When discussing monads, at least, a side effect is an effect that is
triggered by merely evaluating an expression. A monad is an interface
that decouples effects from evaluation.
I don't understand that definition. Or maybe I do subconsciously.
I have
On Sat, Sep 29, 2012 at 8:46 PM, KC wrote:
> http://martinfowler.com/eaaDev/EventSourcing.html
>
> http://martinfowler.com/articles/lmax.html
This notion of "Capture all changes to an application state as a
sequence of events" sounds a lot like what John Carmack did in Quake 3
[1]:
> I settled o
On Sun, Sep 30, 2012 at 6:33 PM, Jake McArthur wrote:
>
> On Sep 30, 2012 10:56 AM, "Albert Y. C. Lai" wrote:
>>
>> On 12-09-29 09:57 PM, Vasili I. Galchin wrote:
>>>
>>> I would an examples of monads that are pure, i.e. no
>>> side-effects.
>>
>>
>> What does "side effect" mean, to you?
On Sep 30, 2012 10:56 AM, "Albert Y. C. Lai" wrote:
>
> On 12-09-29 09:57 PM, Vasili I. Galchin wrote:
>>
>> I would an examples of monads that are pure, i.e. no
side-effects.
>
>
> What does "side effect" mean, to you? Definition?
When discussing monads, at least, a side effect is an ef
Aleksey Khudyakov writes:
> On 13.08.2012 19:43, Ryan Newton wrote:
>> Terrible! Quite sorry that this seems to be a bug in the monad-par library.
>>
>> I'm copying some of the other monad-par authors and we hopefully can get
>> to the bottom of this. If it's not possible to create a smaller
>>
On 9/30/12 7:00 AM, Tillmann Rendel wrote:
Vasili I. Galchin wrote:
I would an examples of monads that are pure, i.e. no side-effects.
One view of programming in monadic style is: You call return and >>= all
the time. (Either you call it directly, or do notation calls it for
you). So if you wa
On 09/30/2012 02:46 AM, KC wrote:
> http://martinfowler.com/eaaDev/EventSourcing.html
>
> http://martinfowler.com/articles/lmax.html
>
>
Sure, why not? See
http://hackage.haskell.org/package/cqrs-0.8.0
and http://hackage.haskell.org/package/cqrs-example-0.8.0
for an example application.
Hi,Marcelo,
No. .Acid state is explcitly managed by the process by means of state
management primitives
In Control.Workflow the state is managed in a implicit way.
It is a monad transformer mainly is designed for wrapping IO computations.
the lifting primitive, step, store the intermediate res
Hi,
On Sun, Sep 30, 2012 at 4:22 AM, Alberto G. Corona wrote:
> It´´s a very iteresting concept.
>
> The Workflow Monad transformer [1], in Control.Workflow perform
> logging and recovery of application istate from the log created.
> It has no implementation of roll-back or limited recovery upto
On 12-09-29 09:57 PM, Vasili I. Galchin wrote:
I would an examples of monads that are pure, i.e. no side-effects.
What does "side effect" mean, to you? Definition?
Because some people say "State has no side effect", and some other
people say "State has side effects". The two groups u
Vasili I. Galchin wrote:
I would an examples of monads that are pure, i.e. no side-effects.
One view of programming in monadic style is: You call return and >>= all
the time. (Either you call it directly, or do notation calls it for
you). So if you want to understand whether a monad "has side
11 matches
Mail list logo
