Yeah, no one seems to know about it, which is surprising to me. I've
been using it for over 2 years and I'd never want to go back. I guess
most people don't mind maintaining import lists, my guess is that few
people work on large projects, so they never see a long import list.
On Mon, Jun 24, 20
Tom Lokhorst and myself worked on a tool to generate missing imports,
both qualified and unqualified, at the Odessa hackathon. We created a
working proof of concept [0]. I wasn't aware of fix-imports.
Erik
[0] https://github.com/haskell-suite/halberd
On Tue, Jun 25, 2013 at 6:30 AM, Evan Laforge
This is neat, it sounds like I could use this with fix-imports to find
only modules that export the right function name, or even to add
non-qualified imports. But since it's already 95% good enough for my
use case, I probably won't get around to it any time soon.
On Thu, Jun 20, 2013 at 8:13 AM,
I took a quick look at this, and came to the conclusion that the scope info
is available from GHC, but is not exposed by HaRe at this stage.
Rather than chasing something just to show it can be done, I am going to
use my limited time for HaRe.
By the way, I think buildwrapper generates a summary
* Andrew Cowie [2013-06-21 16:12:55+1000]
> On Thu, 2013-06-20 at 18:13 +0300, Roman Cheplyaka wrote:
> > Namely, it can do the following:
> >
> > * for a module, compute its interface, i.e. the set of entities
> > exported by the module, together with their original names.
> >
> > * for
I have a feeling the work-in-progress Haskell Refactorer using the GHC API
may be able to provide this information through its library interface.
When I have some time over the weekend I will have a look.
Alan
On Fri, Jun 21, 2013 at 8:44 AM, Michael Sloan wrote:
> Roman: Awesome! I'm really
Roman: Awesome! I'm really glad that this is ready for use!
Andrew: I have a tool that's a step towards doing this. Instead of using
haskell suite, it uses ghci via hint to query module exports, and then uses
TH to reify them. This has the benefit of supporting everything that GHC
supports, whe
On Thu, 2013-06-20 at 18:13 +0300, Roman Cheplyaka wrote:
> Namely, it can do the following:
>
> * for a module, compute its interface, i.e. the set of entities
> exported by the module, together with their original names.
>
> * for each name in the module, figure out what it refers to —
