Conrad Barski's Haskell Tutorial
lisperati.com
Conrad Barski's Haskell Tutorial
1–10 of 42 posts
Re: Conrad Barski's Haskell Tutorial
#2I like the tutorial though. I'd be willing to bet it's his style and work that inspired the "Learn you a..." books. The Haskell one is great, and so is the Erlang one.
Re: Conrad Barski's Haskell Tutorial
#3If you like my stuff, keep an eye out for my new Bitcoin book, which will be coming out this fall. I've been slaving over the artwork for months, it should be a beautiful book! The working title is "Bitcoins for the Befuddled".
Re: Conrad Barski's Haskell Tutorial
#4Re: Conrad Barski's Haskell Tutorial
#5Wow, how did my Haskell tutorial get to the HN front page out of nowhere? :-) If you like my stuff, keep an eye out for my new Bitcoin book, which will be coming out this fall. I've been slaving over the artwork for months, it should be a beautiful book! The working title is "Bitcoins for the Befuddled".
Re: Conrad Barski's Haskell Tutorial
#6It's platform-dependent
h> finiteBitSize (0 :: Int)
64
> We could have used the type Integer instead- This type of integer grows "magically" and can hold any sized integer, no matter how big... but it's slower, so we used Int instead, since our numbers will never get that big.Premature optimisation at its best.
Re: Conrad Barski's Haskell Tutorial
#7ghc 7.6.3 (brew) installed on OS X doesn't like the first code presented (System.Random, Text.Regex and StdGen aren't found).
Re: Conrad Barski's Haskell Tutorial
#8Re: Conrad Barski's Haskell Tutorial
#9Picnicmob was a really clever idea. I think I remember that it got cancelled though, which was unfortunate. I like the tutorial though. I'd be willing to bet it's his style and work that inspired the "Learn you a..." books. The Haskell one is great, and so is the Erlang one.
Re: Conrad Barski's Haskell Tutorial
#10> In Haskell, this type of integer can't get bigger than 2^31... It's platform-dependent h> finiteBitSize (0 :: Int) 64 > We could have used the type Integer instead- This type of integer grows "magically" and can hold any sized integer, no matter how big... but it's slower, so we used Int instead, since our numbers will never get that big. Premature optimisation at its best.