-
-
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
Tone down the implicit cradle import warnings #620
Comments
Or no warnings by setting a config option! I don't think I've ever changed my behavior after getting one of those warnings. |
Or maybe the warnings are no longer necessary? It used to be that an implicit cradle was a guarantee something would go wrong. Nowadays I have way more success with implicit cradles than explicit ones. |
@ndmitchell i was a little bit confused for the
in the description, i suppose you wanted to mean impicit cradle. I think it works well enough to demote it again (was done from warning to info) to a log message |
Oops! Too much time dealing with implicit prelude stuff - thanks for the fix :). Agreed, a log message might be the way to go. |
Your environment
I am using HLS 0.6. Since I installed directly from VS Code I have no HLS or HLS wrapper on my path to probe tools. Windows, VS Code.
Steps to reproduce
Open Shake with no hie.yaml. Observe that each and every file I open produces a warning about an implicit prelude. I just dismissed 25 such warnings.
Expected behaviour
One warning. Once per session seems plenty.
Actual behaviour
Many warnings.
The text was updated successfully, but these errors were encountered: