-
Notifications
You must be signed in to change notification settings - Fork 208
bad module error handling with hlint enabled #1782
Comments
Apparently the upgrade didn't have anything to do with the problem I'm facing. It looks like HIE chokes on my code. To reproduce: Create a new project with
This causes an error indicator to appear on the last line ( |
Hi! Sorry for the late response. |
Ok, i thing the error comes from hlint (the linter used by hie by default). If you turn off the extension option: {
"languageServerHaskell.hlintOn": false
} the problem is gone. hlint has to parse the module too and not always match the compiler parsing. |
Thanks for confirming and providing a workaround. So far I've been hitting the "Haskell: restart HIE" action every now and then. |
After upgrading stack to 2.3.1 yesterday Haskell support in VScode is severely broken:
After opening an empty project created with
stack new myproject
I see "Initializing Stack project" popping on and off in the status bar for many time until it settles.After I edit an Haskell file this starts all over again until finally an error indicator appears for e.g. an variable that is not in scope.
When I fix a problem the error indicators stick around until I close and restart VScode.
The text was updated successfully, but these errors were encountered: