GHC 8.0.1 is available
ghc.haskell.org
GHC 8.0.1 is available
1–10 of 38 posts
Re: GHC 8.0.1 is available
#2The FPComplete guys will probably have it up on Stackage in a few days. You can still use it by adding the tarball to your stack.yml, and maybe adding the 'allow-newer: true' flag:
https://www.reddit.com/r/haskell/comments/4kdb74/is_a_stacka...
I'm looking forward to trying out the new debugging support: gdb was unusable with older GHCs.
Implicit callstacks are cool: Remember that you can hide the parameter inside of your application's main monad:
type MyApplicationM a = (?l :: CallStack) => StateT ConnectionPool IO a
Re: GHC 8.0.1 is available
#3 * The introduction of the DuplicateRecordFields language extension, allowing
multiple record types to declare fields of the same name
One of Haskell's great miseries has been that, because record field accessors are declared globally, you couldn't define records with fields of the same names:
data Person = Person { name :: String, age :: Int }
data Object = Object { name :: String, id :: UUID } -- error! `name` taken
Edit: Info on the extension at: https://ghc.haskell.org/trac/ghc/wiki/Records/OverloadedReco.... Looks like it creates ambiguity in some cases.
Re: GHC 8.0.1 is available
#4* The introduction of the DuplicateRecordFields language extension, allowing multiple record types to declare fields of the same name Holy hell. Is this the end of the Haskell record field names problem? One of Haskell's great miseries has been that, because record field accessors are declared globally, you couldn't define records with fields of the same names: data Person = Person { name :: String, age :: Int } data…
As a recent beginner to Haskell, are there other big outstanding issues with the GHC to watch out for?
Re: GHC 8.0.1 is available
#5* The introduction of the DuplicateRecordFields language extension, allowing multiple record types to declare fields of the same name Holy hell. Is this the end of the Haskell record field names problem? One of Haskell's great miseries has been that, because record field accessors are declared globally, you couldn't define records with fields of the same names: data Person = Person { name :: String, age :: Int } data…
As a recent beginner to Haskell, are there other big outstanding issues with the GHC to watch out for?
The record issue is a widespread inconvenience, but ultimately nothing more than an inconvenience. Most people just prepended the type in their fields: 'person_name' and 'object_name'.
Some other issues might be:
* The Prelude is hard to update for compatibility reasons, so it clashes with modern Haskell somewhat. A lot of projects will roll their own prelude and add 'NoImplicitPrelude' to the project options.
* There's also this presentation: https://secure.plaimi.net/~alexander/tmp/pres/2016-05-11-why...
* Deploying Haskell programs to older corporate servers is doable, but not at all obvious. Stick with C, Bash, and older Perls(5.8.8 is on my router) for maximum portability, if you expect to deploy to servers with a 10 year old image.
Re: GHC 8.0.1 is available
#6* The introduction of the DuplicateRecordFields language extension, allowing multiple record types to declare fields of the same name Holy hell. Is this the end of the Haskell record field names problem? One of Haskell's great miseries has been that, because record field accessors are declared globally, you couldn't define records with fields of the same names: data Person = Person { name :: String, age :: Int } data…
The ambiguity can be resolved by type annotations, so I think that this won't cause much pain in practice.
Re: GHC 8.0.1 is available
#7* The introduction of the DuplicateRecordFields language extension, allowing multiple record types to declare fields of the same name Holy hell. Is this the end of the Haskell record field names problem? One of Haskell's great miseries has been that, because record field accessors are declared globally, you couldn't define records with fields of the same names: data Person = Person { name :: String, age :: Int } data…
As a recent beginner to Haskell, are there other big outstanding issues with the GHC to watch out for?
[deleted]
Re: GHC 8.0.1 is available
#8The new Sphinx based documentation has many code sample boxes where the content overflows and the rectange is smaller than the text which doesn't fit into the rendered HTML/PDF. Is this a common issue with Sphinx?
Re: GHC 8.0.1 is available
#9Earlier quoted context omitted.
As a recent beginner to Haskell, are there other big outstanding issues with the GHC to watch out for?
The record issue is a widespread inconvenience, but ultimately nothing more than an inconvenience. Most people just prepended the type in their fields: 'person_name' and 'object_name'. Some other issues might be: * The Prelude is hard to update for compatibility reasons, so it clashes with modern Haskell somewhat. A lot of projects will roll their own prelude and add 'NoImplicitPrelude' to the project options. * Ther…
Regarding deployment, why not just link statically? http://stackoverflow.com/a/5953787/309483
Re: GHC 8.0.1 is available
#10Earlier quoted context omitted.
As a recent beginner to Haskell, are there other big outstanding issues with the GHC to watch out for?
The record issue is a widespread inconvenience, but ultimately nothing more than an inconvenience. Most people just prepended the type in their fields: 'person_name' and 'object_name'. Some other issues might be: * The Prelude is hard to update for compatibility reasons, so it clashes with modern Haskell somewhat. A lot of projects will roll their own prelude and add 'NoImplicitPrelude' to the project options. * Ther…
we've deployed modern haskell onto RHEL 6.5 systems at work, and thats not too bad (just some dy load library path hackery at worst)