Open phlummox opened 4 years ago
Hi,
Am I doing something wrong, or is this the expected behaviour? Given how common it is in Haskell to call functions with an explicit module name (possibly re-named), this seems like a bit of a drawback to using hscope in practice if it can't handle this situation.
There is a very good change that you've found bug here.
As you have probably noticed, I do not do much work on hscope anymore and have no time to investigate right now.
Will be happy to merge patches though :)
Ah, no worries. I'll submit a patch if I work out a fix - but mostly I was just experimenting to see if hscope would be a good addition to my Vim environment.
I am trying hscope and have hit a stumbling block. I might be doing something wrong, but, by way of a minimal example, I write the following three modules:
So, there are 2 modules that call
someFunc
, but one calls it asF.someFunc
.I build an hscope database with (adding "-v" to see exactly what's happening):
I query what functions call "someFunc":
What I'd expect is for the references to both UsesFoo and UsesFoo2 to show up. Re-naming modules on import (
import Foo as F
) in Haskell is ubiqitous, barely a program exists that doesn't do this.Yet the result I get only shows UsesFoo2:
Am I doing something wrong, or is this the expected behaviour? Given how common it is in Haskell to call functions with an explicit module name (possibly re-named), this seems like a bit of a drawback to using hscope in practice if it can't handle this situation.