|
Boost : |
Subject: [boost] Why a concrete monad class? (was Re: [next gen futures] Lightweight monad ready for inspection)
From: Vicente J. Botet Escriba (vicente.botet_at_[hidden])
Date: 2015-06-29 11:54:19
Le 29/06/15 12:35, Niall Douglas a écrit :
Niall, I don't see why do you need to define a concrete monad class that
is used to define other monadic types. The implementation of each
specific monadic type has its own trade-offs.
We can provide monadic operations for optional/expected/future/....
Why do you need to have a concrete monad class?
What is the added value?
Best,
Vicente
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk