GHCup: Because #Haskell apparently needs a package manager for its various package management systems.
Jeremy List likes this.
I'm an idiot.
I was trying to install #Haskell on a machine and thought the installer was taking a really long time. In my defense, the last line of text was:
Installation may take a while.It sat at this stage for over an hour while I did other stuff, because I hadn't bothered to read the previous line:
Press ENTER to proceed or ctrl-c to abort.like this
in reply to Jonathan Lamothe
It's not you, it's bad design. The prompt should always be the final line of output.
Jonathan Lamothe likes this.
Did #Haskell at some point make defining a module without an explicit list of names to be exported illegal? It's yelling at me when I try to do this now.
in reply to Jonathan Lamothe
I noticed a while ago that they added a warning for that but it would still compile, but I wouldn't be completely surprised if it were an error now.
It's actually annoying in ghci because the warning gets repeated every time you define something.
It's actually annoying in ghci because the warning gets repeated every time you define something.
in reply to Jeremy List
@Jeremy List No, it's still just a warning. I was using the
--pedantic flag though (which turns warnings into errors).Jeremy List likes this.
in reply to Boyd Stephen Smith Jr.
@Boyd Stephen Smith Jr. It's not so much the SQL part that's the irritating bit. It's that it doesn't really mesh super well with "the Haskell way of doing things".
like this
in reply to Jonathan Lamothe
@BoydStephenSmithJr understandable. There's always a tension between "pleasant for the Haskeller" and "pleasant for the DBA" (or general SQL knower). We have the same problem at work (we sacrificed our DBA and used https://flora.pm/packages/@hackage/hpqtypes-extras and its eDSL)
Grégoire Locqueville
in reply to Jonathan Lamothe • • •Digit
in reply to Jonathan Lamothe • • •