Hi Daniel,
If I'm getting this correctly, than Halberd uses some kind of static database, right?
Right.
I think the nice approach of 'vim-hsimport' is, that by using 'hdevtools' in conjunction with a 'cabal sandbox', only the modules of the packages are considered, which your project depends on, and this information is dynamically "established" by 'hdevtools' reading the package database of the 'cabal sandbox'.
I recall Erik and others discussing ways of restricting halberd to a sandbox as well, but you'd have to ask him about the progress. Cheers, Adam On Sun, Dec 29, 2013 at 1:30 PM, Daniel Trstenjak < daniel.trstenjak@gmail.com> wrote:
Hi Adam,
You may also be interested in Halberd[1][2] which uses hs-gen-iface[3] to do automatically insert missing imports by finding modules with the desired names. It does not have a vim plugin yet, but I imagine a simplistic one should be easy to make.
If I'm getting this correctly, than Halberd uses some kind of static database, right?
I think the nice approach of 'vim-hsimport' is, that by using 'hdevtools' in conjunction with a 'cabal sandbox', only the modules of the packages are considered, which your project depends on, and this information is dynamically "established" by 'hdevtools' reading the package database of the 'cabal sandbox'.
But I have to confess, that hsimport/vim-hsimport are still in a quite early stage.
Greetings, Daniel _______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe