Remove unused function testCase generating warning when compiling test modules.#146
Remove unused function testCase generating warning when compiling test modules.#146kytrinyx merged 1 commit intoexercism:masterfrom rbasso:unused-testcase
Conversation
Removed code:
- function testCase
- import of Assertion
Affected exercises:
atbash-cipher
binary
crypto-square
hexadecimal
largest-series-product
nth-prime
prime-factors
raindrops
roman-numerals
scrabble-score
triangle
|
I can't think of a reason to keep the code that (a) we are not using and (b) causes a warning. @towynlin Is there something here that I'm missing? |
|
Now you are getting me curious as to why Travis doesn't fail without this PR, as we do run tests with Experimenting quickly on my machine, some raw results:
As for this PR: The pattern we will see is that we'll have two lines mentioning (further entries omitted, we are only interested in entries with 2 lines, that means we also don't touch sgf-parsing) this seems to match the list in this PR, so this all seems good - it is certain that |
|
I imagine the reason why The only test files that don't have So probably some copy paste that includes |
|
Same result here regarding I got the warnings because I have a very different setup here. I don't like the use of a global installation of GHC with the packages provided by I really prefer |
|
To me personally, it seems valuable to track dependencies per exercise instead of globally. I definitely took that approach for a different project with multiple self-contained problems. I wonder if one day that would be an appropriate thing to do for this repo. I realize what I said is not really relevant to this PR so maybe suited for a different issue. |
|
Thanks for pinging me @kytrinyx — haven't found the time to review yet. Good discussion here. Keep it up folks. I'm not hearing a conclusive merge/close call from the discussion yet. If anybody is confident one way or the other, please say so! |
|
For what it's worth, I would support merging this. |
|
We where just discussing others issues in the wrong place. Sorry! |
|
Cool, in that case... :merge: |
|
I see — finally got a minute to glance over the code. Appreciate your |
Some exercises show a warning when compiling the test module:
This can confuse users and is not considered good practice.
Unused code:
testCaseAssertionAffected exercises:
Closes #145