intoverfl0w

5 ms·

1. 1.▲
   by intoverfl0w 16y ago

   Couldn't agree more on all points, particularly the last two.
2. 2.▲
   by intoverfl0w 16y ago

   Here's some code: {-# LANGUAGE TypeFamilies, MultiParamTypeClasses, FlexibleInstances #-} data True = T data False = F class LogicOr a b where type Or a b typeOr :: a -> b -> Or a b
3. 3.▲
   Quasi-quoting: ASCII art to define data structures(potential-lang.org)

   4 points by intoverfl0w 16y ago|1 comments
4. 4.▲
   by intoverfl0w 16y ago

   Laziness is one of those features I can never make my mind up about. It is sometimes very convenient, but most of the time I never think about the fact that the semantics mean evaluation is lazy. Sometimes this negligence has bad conseque
5. 5.▲
   by intoverfl0w 16y ago

   If you work in a .Net environment and want to explore the possibility of using functional programming on the job, F# is definitely a natural way to go. Depending on how much autonomy you have at work, Haskell is a reasonable language for ge
6. 6.▲
   by intoverfl0w 16y ago

   (author here). This is good feedback. I definitely struggled with finding a good way to describe what each of the features does. I'm considering writing a sequence of followups, each focusing on a particular feature, trying to describe h