Subject: Re: [boost] [next gen future-promise] What to call the monadic return type?
From: Niall Douglas (s_sourceforge_at_[hidden])
Date: 2015-05-26 10:47:37
On 26 May 2015 at 10:02, Lee Clagett wrote:
> But if the major complaint about Expected is the compile-time, what is
> causing that compile-time, and how will this new type avoid that?
This monad is ridiculously simple because it's fixed function
variant, and instantiates exactly two types per instance, and
currently two free function overloads. No partial specialisations at
all. There will be R& and void specialisations later, but they are
all hash lookups, not shortlisting lookups in the compiler.
Expected instantiates dozens of types and functions per instance.
Lots of partial specialisations too. All of that is very slow and
involves lots of generating shortlists and iterating them for closest
overload match. Slow.
-- ned Productions Limited Consulting http://www.nedproductions.biz/ http://ie.linkedin.com/in/nialldouglas/
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk