On 29 Aug 2015 3:07 am, "Niall Douglas"
On 28 Aug 2015 at 12:02, Giovanni Piero Deretta wrote:
Could you show us a custom policy implementation for a list monad?
As I mentioned earlier, it's not a full monadic programming solution by any stretch. Think of it as a value transporter with monadic extensions, very similar to the Rust Monad.
... You just claimed that:
"It's a framework for creating bespoke future and monad types."
I'm not seeing what the problem is here. It is as I described.
How can it be both a "framework for creating bespoke monads" and at the same time " not a full monadic solution". I either can create a monad - any monad - with it or not.
Also what's the rust monad you are referring to?
Search google for the Rust programming language and Option<T> and Result<T>.
Those aren't in any way rust monad. They are specific implementations of a monad concept, which incidentally can't be encoded yet as a rust Trait as Rust doesn't have yet a type system powerful enough. -- gpd