-
Updated
Dec 23, 2020 - Haskell
ghc
Here are 138 public repositories matching this topic...
Is your feature request related to a problem? Please describe.
This is the tracking issue for the Asterius Hackage Overlay.
Describe the solution you'd like
We should implement and host a Hackage overlay, similar to head.hackage and mobile haskell overlay. The reason is:
- We already patch so
-
Updated
Jan 4, 2021 - Haskell
-
Updated
Mar 7, 2022 - Haskell
-
Updated
Jan 23, 2022 - Haskell
-
Updated
Sep 21, 2021 - TypeScript
-
Updated
May 18, 2021 - Shell
A good alternative to having all the explanations in comments in the exercise files would be to make a Markdown file for each exercise (or possibly each category of exercises, i.e. one for each sub-directory). These files would contain the exact text from the explanation blocks except formatted to Markdown. There should also be a link in the exercise file to the Markdown and vice-versa. There shou
-
Updated
Dec 10, 2021 - Haskell
-
Updated
Jan 15, 2021 - Haskell
-
Updated
Jun 11, 2018 - Haskell
-
Updated
Mar 6, 2022 - Haskell
-
Updated
Feb 26, 2022 - Haskell
-
Updated
Oct 7, 2018 - Haskell
Improve this page
Add a description, image, and links to the ghc topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the ghc topic, visit your repo's landing page and select "manage topics."
When completing a type signature HLS is very conservative and always adds parentheses around the actual type.
For example something like
myHead :: [a] -> _will get a type ofmyHead :: [a] -> (a). Note the parentheses around the a.While I personally don't have a big problem with this. Many of my colleagues insist on them being removed. Which usually makes these signatures easier to read