Re: How to exploit ./hadrian/ghci to find errors quickly?

2022-02-02 Thread Norman Ramsey
> > [Finding the locations of compiler errors after a change] > > This is the typical use case for a language server. > I have haskell-language-server installed and use it extensively on GHC > for stuff like jump to definition and immediate compilation feedback. > > There's also "jump to

Re: How to exploit ./hadrian/ghci to find errors quickly?

2022-02-01 Thread Norman Ramsey
> The Binary runGet issue usually means that your build tree is out of date. > It's probably worth deleting and building from scratch again. For those who may come after me: if ./hadrian/ghci barfs with a Binary runGet issue, the build tree that needs to be deleted is `.hadrian_ghci`, not

Re[2]: How to exploit ./hadrian/ghci to find errors quickly?

2022-01-29 Thread Sebastian Graf
? Not sure. Anyway, if HLS behaves strangely, try deleting its build root. Sebastian -- Originalnachricht -- Von: "Norman Ramsey" An: "Sam Derbyshire" ; ghc-devs@haskell.org Gesendet: 29.01.2022 00:34:23 Betreff: Re: How to exploit ./hadrian/ghci to find errors quic

Re: How to exploit ./hadrian/ghci to find errors quickly?

2022-01-28 Thread Norman Ramsey
> The Binary runGet issue usually means that your build tree is out of date. > It's probably worth deleting and building from scratch again. Brilliant! Definitely working much better! And @Sebastian I start to see the productivity gains. Remove all redundant imports with one click! Norman

Re: How to exploit ./hadrian/ghci to find errors quickly?

2022-01-28 Thread Sam Derbyshire
The Binary runGet issue usually means that your build tree is out of date. It's probably worth deleting and building from scratch again. ___ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: How to exploit ./hadrian/ghci to find errors quickly?

2022-01-28 Thread Norman Ramsey
> This is the typical use case for a language server. > I have haskell-language-server installed and use it extensively on GHC > for stuff like jump to definition and immediate compilation feedback. I would *love* to be doing this. I have had HLS installed on my machine for months, and have

Re: How to exploit ./hadrian/ghci to find errors quickly?

2022-01-28 Thread Sebastian Graf
ys already. Sebastian -- Originalnachricht -- Von: "Norman Ramsey" An: ghc-devs@haskell.org Gesendet: 28.01.2022 17:52:00 Betreff: How to exploit ./hadrian/ghci to find errors quickly? > My recommendation: ./hadrian/ghci. Richard, this suggestion has been so useful that

Re: How to exploit ./hadrian/ghci to find errors quickly?

2022-01-28 Thread Tom Ellis
On Fri, Jan 28, 2022 at 11:52:00AM -0500, Norman Ramsey wrote: > > My recommendation: ./hadrian/ghci. > > I'm about to change a type definition. This change may wreak havoc in > many parts of GHC, and this is exactly what I want: I'm looking for > type-error messages that will tell me what

How to exploit ./hadrian/ghci to find errors quickly?

2022-01-28 Thread Norman Ramsey
> My recommendation: ./hadrian/ghci. Richard, this suggestion has been so useful that I would like to follow it up. I'm about to change a type definition. This change may wreak havoc in many parts of GHC, and this is exactly what I want: I'm looking for type-error messages that will tell me