Prevent leakage of warnings from configuration#52
Prevent leakage of warnings from configuration#52patritzenfeld wants to merge 2 commits intomasterfrom
Conversation
|
Doesn't it prevent I think we want the sample solution to be allowed to use What we want to prevent is that the students get to see warnings about |
|
(Which could be achieved by making it so that the test suite is not allowed to use |
|
Would it be enough to always enforce the config rules for interpreter runs, thus changing those that are running with "default settings" (mentioned in #13 (comment)) to also use the config and not any additional warnings enabled by Or do you explicitly want |
|
Yes, that would probably solve it. I didn't want |
closes #13
-Wall, this also indirectly covers-Wextended-warningsand therefore-Wx-partialThis should make sure the configs are warning free.
@jvoigtlaender this is a bit different from what you last suggested in #13, but I think it accomplishes the same goal. The config should fail on one of the interpreter runs respecting the config GHC options with
-Wallif it would fail in one of the compiles ignoring the options. Do you see any problems with this approach?