-
-
Notifications
You must be signed in to change notification settings - Fork 389
(Question) Compile errors across multi-cradle projects #2035
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
Comments
Dont worry, all questions are welcomed and no one is trivial, moreover if you has take a look to docs and did not find a clear answer. |
Thank you for the answer. I am asking because I started questioning whether my set-up is OK. It seems that I might have a problem somewhere after all as compile errors remain (or do not appear) in my test and executable projects if I make a change in the library. For example, renaming a function in the library is not "visible" in the executable: an error does not appear in the problems pane of VS Code.
Should I be looking somewhere else for the cause of this behavior? |
Ok, could you attach the logs mentioned in the issue template?
|
I followed the following steps:
|
This seems to be a manifestation of #366 so closing, @Savelenko thanks! |
I have a general question which seems kind of stupid and trivial, but I did not find any mention of this in documentation. Should code analysis work across different components in a multi-cradle project? Say adding an
Eq
instance in the library project such that an error "immediately" disappears in a test module?Probably not necessary, but my set-up is VS Code,
stack
, HLS 1.2 and GHC 8.8.4 and an explicithie.yaml
with a library, executable and test components.The text was updated successfully, but these errors were encountered: