- August 20th, 2016: maybeify :: (a, Maybe b) -> Maybe (a, b)

Define maybeify. Snaps for elegance. - Hardy Jones @st58 sequence
- Bruno @Brun0Cad mapM id
- Thomas D @tthomasdd {-# LANGUAGE TupleSections #-}

mabeify (x,mY) = maybe Nothing (return . (x,)) mY - Андреев Кирилл @nonaem00 import "category-extras" Control.Functor.Strong

maybeify = uncurry strength - bazzargh @bazzargh I can't beat 'sequence', but: uncurry (fmap.(,))
- Nick @crazy_fizruk distribute (from Data.Distributive)

## Thursday, September 15, 2016

### August 2016 1HaskellADay 1Liners

## Thursday, September 1, 2016

### August 2016 1HaskellADay Problems and Solutions

###
**August 2016**

- August 31st, 2016: Today's #haskell problem we prepare Merkle trees (used by #blockchain/#Bitcoin) by hashing data, then hashing hashes. Wow! That was a lot of hash...ing! SHA256 #crypto #Bitcoin #blockchain used for today's #haskell solution
- August 30th, 2016: In today's #haskell exercise we look at #bitcoin mining machines comparing cost, efficiency and potential BTC found. Today's #haskell solution compares #bitcoin mining hardware ... by deriving a theorem of logic. Yeah. So: that.
- August 29th, 2016: For today's #haskell problem we find the next number in a series. Then @JMVarnerBooks asks for an efficient encoding. A little bit of group, a little bit of compress, and we have today's #haskell solution. YES!
- August 26th, 2016: Today's #haskell problem continues with currencies, looking at gold, then comparing #bitcoin

Today's #haskell solution
looks at gold then compares to #bitcoin and generalizes recursion

Today's #haskell solution is worth $180k ... five years ago. I wonder what it will be worth 5 years hence?

Okay! For today's #haskell solution we discover our node and relation types in twitter data-as-graphs JSON!

Okay, we have a #Haskell solution ... finally ... maybe. The solver took too long, so I solved it myself faster :/

Subscribe to:
Posts (Atom)