Re: ModuleInfo.minf_rdr_env not exposed

2019-08-06 Thread Artem Pelenitsyn
Hey Sam, I think the thing you propose hardly qualifies as a new feature (in the sense of page you referenced), so not much of a hassle should be involved. As long as it is a 3-lines change, I'd say go ahead and create an Issue and an MR on Gitlab: you might be better off with getting feedback

Re: ModuleInfo.minf_rdr_env not exposed

2019-08-06 Thread Sam Halliday
Hello, I would like to submit a patch to ghc 8.8 adding a function that exposes a field that is useful for tooling authors and can already be reached, albeit in a very awkward way. The process documented at https://gitlab.haskell.org/ghc/ghc/wikis/working-conventions/adding-features seems very

Re: Conveniently searching GitLab

2019-08-06 Thread Brandon Allbery
You can define them in the settings; what's odd about them is that it's part of "Manage search engines". Which is at the bottom of the right click menu in the location bar (with "edit" instead of "manage", so it should be just as easy to do. On Tue, Aug 6, 2019 at 12:41 PM Ben Gamari wrote: >

Re: Conveniently searching GitLab

2019-08-06 Thread Ben Gamari
Ben Gamari writes: > Hello everyone, > ... > * search for merge requests of `haskell/ghcup` pertaining to Darwin: >search for `haskell/ghcup! Darwin` > Unfortunately this example doesn't quite work as I haven't implemented the necessary logic to lookup project IDs from project names. I

Conveniently searching GitLab

2019-08-06 Thread Ben Gamari
Hello everyone, I've long found GitLab's search interface to be rather clunky. Several of the issues I've noted have been reported upstream but progress in resolving them seems to be slow. Consequently, I have implemented a workaround [1] which addresses most of my typical use-cases. This is