My new #Haskell setup
Fancy recursion schemes are often mere catamorphisms in disguise.
#Haskell job description I'd like:
Having fiddled with a new FRP wrapper for code.world/haskell and *not* using Events/Behaviors/Dynamic in fullest it kinda dawned on me how composition in The Elm Architecture (that I kinda liked) is 1) different 2) related and 3) awkward.
More practice is needed though.
Neon Typeclass Evangelion #Haskell
`Map.fromList` considered harmful.
And other funny functions that silently discard data.
It works as a system-wide resolver, having a fallback delegation, but the damn browsers are still refuse to use it for good. Too much smarts, caching and "security" levels piled on top of each other.
> Parsec: “try a <|> b” considered harmful
> tl;dr The scope of backtracking try should be minimized, usually by placing it inside the definition of a parser.
Avoid non-total functions in Prelude at all costs.
Two things fill the mind with ever new and increasing admiration and awe, the more often and steadily we reflect upon them: storing providence in your types and instances for `Data.Tree.View`.
Mu (forall a. (f a -> a) -> a)
Nu :: (a -> f a) -> a -> Nu f
Pure a | Free (f (Free f a))
... these a few of my favorite Fix
Patterns? Where we're going, we don't need patterns.
Ceci n'est pas un twitter.
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!