-
Notifications
You must be signed in to change notification settings - Fork 846
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
stack ghci
succeeds (with warnings) despite hidden packages
#2333
Comments
I just hit this issue again. I'm not sure what kind of errors apart from hidden modules are converted to warnings at this spot, but at least for hidden modules, I'd be in favor of actually erroring out. The problem is easy enough to fix for the user but can be surprising and annoying at a later point. |
Hmm, I cannot reproduce. How is stack invoking ghc? Here's what's in my verbose log:
Note that |
So you don't even get the hidden module warning? Here's most of my log:
|
I get the following:
|
@sjakobi Is this still happening with the latest HEAD version of stack? |
Yes, now even the hidden package warning from Here's the verbose log of the full repro. Here's the ghci invocation:
My expectation still is, that |
Something seems fishy here. Note that
We cannot, and have not made that guarantee. For one thing, we mix up all the flags from multiple components. The lack of warning is due to the resolution of #1364 |
What I expected: The command fails.
What actually happened:
Now, there is a warning, which is good. But if you're using, for example, ghcid, that warning might not be visible to you.
I think it would be better to fail in this case, but maybe I'm overlooking some technicalities of ghci here?
The text was updated successfully, but these errors were encountered: