[Haskell-cafe] about Haskell code written to be "too smart"
conal at conal.net
Tue Mar 24 18:40:38 EDT 2009
We live in the age of participation -- of co-education. Don't worry about
text-books. Contribute to some wiki pages & blogs today that share these
smart techniques with others.
<twocents>Learning/progress is mainly results when people respond to their
own incomprehension by moving into new & challenging ideas, not by banishing
them. Puzzlement can be met by resistance or by embracing &
On Tue, Mar 24, 2009 at 3:15 PM, Manlio Perillo <manlio_perillo at libero.it>wrote:
> Dan Piponi ha scritto:
>> Miguel Mitrofanov wrote:
>>>> takeList = evalState . mapM (State . splitAt)
>> However, ironically, I stopped using them for pretty
>>> much the same reason that Manlio is saying.
>> Are you saying there's a problem with this implementation? It's the
>> only one I could just read immediately.
> Yes, you understand it immediately once you know what a state monad is.
> But how well is introduced, explained and emphasized the state monad in
> current textbooks?
> When I started learning Haskell, the first thing I learned was recursion
> and pattern matching.
> So, this may be the reason why I find more readable my takeList solution.
> > [...]
> Haskell-Cafe mailing list
> Haskell-Cafe at haskell.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Haskell-Cafe