-
Notifications
You must be signed in to change notification settings - Fork 207
Possible to use additional ghc-option "-fplugin=X"? #1264
Comments
What about as a workaround if you put it as an |
Yeah, I had tried that as a workaround but unfortunately it didn't work; it gave the same compile error in my IDE as if it wasn't there. |
I don't understand really how the the pragma would be ignored if it was in the source file. Would be good to see if anyone else can reproduce this. |
I was a bit surprised by that too; I can provide a repo with an example a bit later tonight. |
I will try to reproduce it. |
Test repository: polysemy-hie-experiment Output of Hie
|
We are probably missing the call which initialises plugins. When the |
will try! |
Just linking back to the polysemy issue so that I can be notified when this gets solved! polysemy-research/polysemy#53 |
Issue is addressed in #20 |
Closed by #1293 |
My current issue: I'm working on code that uses Polysemy, which uses a custom plugin to drive some type inference. This is usually enabled by adding
-fplugin=Polysemy.Plugin
to ghc-options section of cabal file; see https://github.com/isovector/polysemy/tree/master/polysemy-plugin.However, it looks like when HIE is running through my IDE (currently VSCode), it's not using this plugin
ghc-options
override so I see compile errors in my IDE even though there aren't any when compiling through command line.Is there a way to specify additional GHC options like this custom plugin when interfacing with HIE?
The text was updated successfully, but these errors were encountered: