Re: How to exploit ./hadrian/ghci to find errors quickly?
> 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 ___ 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?
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?
> 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 been using with Emacs. But to say I have trouble getting it work as advertised is an understatement. For example, on the module I'm trying to diagnose, I'm getting just one error message, on the first line: Data.Binary.Get.runGet at position 1844: not enough bytes > There's also "jump to next error" if you want that. I can't find it using either "C-h f" or using the list of keybindings at https://emacs-lsp.github.io/lsp-mode/page/keybindings/. I think it might be supported by flycheck, but "C-x `" simply says "No more Flycheck errors." In general, my experience is "sometimes it works and sometimes it doesn't." Even for things as simple as "M-." (find definition). If you know of any resources on using HLS with GHC, I'd love to be directed. For example, when Emacs asks if I really want to watch circa 5,000 directories, do I say "yes"? > The hour or so I invested on initial setup has probably saved me several > days already. I am **so eager** to get there. But definitely not there yet. Norman ___ 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?
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 next error" if you want that. Installation was pretty trivial for me, just flipping this switch in my local ghc.nix clone: https://github.com/alpmestan/ghc.nix/blob/88acad6229300d8917ad226a64de80aa491ffa07/default.nix#L19 You will probably have to install an LSP plugin for emacs first. The hour or so I invested on initial setup has probably saved me several days 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 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 what code I need to fix. I do this work in emacs using `M-x compile` and `next-error`. The key property is that `next-error` requires just a couple of keystrokes (C-x `) and it makes Emacs take me to the relevant source-code location quickly. But telling `M-x compile` to run `./hadrian/build` is quite slow. Is there a way to leverage `./hadrian/ghci` for this workflow? Norman ___ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs ___ 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?
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 code I need to fix. > I do this work in emacs using `M-x compile` and `next-error`. The key > property is that `next-error` requires just a couple of keystrokes > (C-x `) and it makes Emacs take me to the relevant source-code > location quickly. > > But telling `M-x compile` to run `./hadrian/build` is quite slow. Is > there a way to leverage `./hadrian/ghci` for this workflow? Are you familiar with dante-mode for Emacs? It relies on ghci behind the scenes to point out type errors in Emacs Haskell buffers. You might find it convenient even if only for this single-purpose use case. I wrote up how I use dante: http://h2.jaguarpaw.co.uk/posts/how-i-use-dante/ You will have to `M-x customize-group dante` to set the GHCi path to `.../hadrian/ghci`. Tom ___ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
How to exploit ./hadrian/ghci to find errors quickly?
> 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 what code I need to fix. I do this work in emacs using `M-x compile` and `next-error`. The key property is that `next-error` requires just a couple of keystrokes (C-x `) and it makes Emacs take me to the relevant source-code location quickly. But telling `M-x compile` to run `./hadrian/build` is quite slow. Is there a way to leverage `./hadrian/ghci` for this workflow? Norman ___ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
Re: 9.2.2 release schedule?
On Fri, Dec 24, 2021 at 1:31 PM Ben Gamari wrote: > Shayne Fletcher writes: > > > Anyone know of any scheduling plans for ghc-9.2.2? > > > It should be out by mid-January. There are quite a few > backports that we need to push through and the focus recently has been > on finalizing 9.0.2 but I'll be turning my attention to 9.2.2 after I > the holiday. > > g'day again ben :) what's the latest? -- Shayne Fletcher ___ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
Re: meaning of title of merge request on gitlab?
As far as I understand, WIP and Draft are equivalent. ___ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
meaning of title of merge request on gitlab?
I've opened a very, very preliminary MR. The Commentary instructs me to tag it "WIP: ", but gitlab seems to suggest that in order to prevent it from being merged, I need "Draft: ". When a merge request is both WIP and Draft, how should it be titled? (The MR in question is https://gitlab.haskell.org/ghc/ghc/-/merge_requests/7442) Norman ___ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
