-
-
Notifications
You must be signed in to change notification settings - Fork 367
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Parser error on the -- $
chain of characters
#148
Comments
Indeed, this is the same root cause. E.g. running
I am not familiar with how HLS is managed: should we keep this issue open? Or close it as it is "only" an underlying issue? |
Keep it open, so that others see that the issue is known and even being worked on. |
As explained in https://github.com/digital-asset/ghcide/issues/573#event-3423705019 the root cause is Haddock failing + Ghcide considering (in the past) Haddock parsing errors as errors (now downgraded to warnings + "Haddock" is now visible in the error message. I guess this issue can be closed as soon as HLS refers to a version of GHCIDE with this commit |
I just tested with HLS 0.3 and the issue seems to be fixed, I propose we close this. Thank you everyone! |
* Use a separate finder cache for each typecheck call On a large DAML project, we occasionally saw error about missing modules during typechecking during concurrent compilations. This was caused by the fact that we modified the IORef in the HscEnv which is shared between concurrent compilations.
While trying to fix the
hie.yaml
for #121 I noticed 2 tests have a parsing error.The guilty seems to be the
-- $
chain of characters in an implementation of functionMinimal example:
The line
-- $ some other comment
has an error:The text was updated successfully, but these errors were encountered: