borar Profile picture
Jul 17, 2020 14 tweets 8 min read Read on X
I write #fsharp and #haskell daily (and #purescript too) and thought of making a micro-blog comparison of the two. Fun facts and maybe new discoveries for the interested, in no particular order. This will be long and probably slow.
Unlike #fsharp, #haskell has no records, only discriminated unions. It does have something called “record syntax” for DUs.
In #fsharp functions cannot be overloaded. In #haskell it is possible through the “type classes” mechanism, conceived specifically for this.
#fsharp compiler derives (generates) equality for user-defined types with an opt-out option. #haskell can also derive equality, but it is opt-in. So by default values of the same time cannot be equality-compared in Haskell.
Modules in #haskell are both better and worse than in #fsharp. One convenient feature is that a module (say A) can re-export another module (say its dependency B). Clients of A then don’t have to import B to use something from it alongside stuff from A.
Pattern matching is more powerful in #fsharp than in #haskell which lacks AND and OR patterns.
In #fsharp all types are declared using the uniform keyword “type”. In #haskell there are actually three related keywords: “type”, “data” and “newtype”.
#fsharp is compiled to .NET IL and after that subject to JIT compulation by the runtime. #haskell is fully AOT compiled to native binaries.
As per CLR normal, #fsharp preserves type information in compiled output. #haskell performs type erasure. This means, a.o. that there is no run-time reflection possible in Haskell.
White space is significant both in #fsharp and #haskell.
In #fsharp there are separate ‘map’ functions for lists, options and so on. Similarly for ‘filter, ‘fold’ and many more. In #haskell there is (effectively) a single “map” function, but it is polymorphic enough to work with all “mappable types”.
In #fsharp mutable variables are marked with keyword "mutable". In #haskell mutable variables have a dedicated type.
Despite the above tweet, unlike #fsharp, #haskell is famously a pure FP language. Even more famously, it is the only(?) widely used, general purpose PL with lazy evaluation.
Both #fsharp and #haskell have algebraic data types (ADT). In addition, Haskell also has "Generalized ADT" (GADT). Basically in F# terms, one can define a polymorphic DU like FormInput<'a>, but DU constructors limit what 'a can be, e.g. 'int' or 'string' and nothing else.

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with borar

borar Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @Savlambda

Sep 10, 2020
Phantom types usable from future modules. Very simple or I am missing something... @isaac_abraham gist.github.com/Savelenko/37fd…
OK, not really phantom. In between dreams and reality.
Never mind, the proof can be illegally copied. This is garbage.
Read 4 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Don't want to be a Premium member but still want to support us?

Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us!

:(