Richard Eisenberg writes:
> Hi devs,
>
> I have migrated to use VSCode instead of emacs. There are the usual
> switchover pains, but I'm mostly pleased. One particular point of pleasure
> was that I had to do nothing, at all, to get VSCode working within the GHC
> code base. (Well, I had to sw
For ghc dev I generally disable tools / plugins that do indexing.
Especially if I’m on a laptop. The non cabalized builds tend to create a
huge build/indexing overhead and some of these integrations have a blocking
semantics. Plus underdocumented caching so there’s no “prebuilt index” as a
warm sta
Hi Richard,
great to hear, I've also seen a tweet about new videos from you using VS
code (had no time to watch yet).
Hope that more adoption improves things!
So, I've been using VS Code for almost a year now and I have seen great
improvements - almost all of that is the Haskell LSP.
"processing
Hi devs,
I have migrated to use VSCode instead of emacs. There are the usual switchover
pains, but I'm mostly pleased. One particular point of pleasure was that I had
to do nothing, at all, to get VSCode working within the GHC code base. (Well, I
had to switch to Hadrian, but perhaps that's for
Those errors in both logs seem fairly odd. The first one appears to be
mostly a missing libgmp, the second one looks like hsc2hs's template file
is missing, however hadrian should have a rule for that.
You can try to clean your tree and rebuild.
git clean -xfd
git submodule foreach git clean -xfd