Thanks for the feedback @zantetsuken88 - I'll relay this info to the other track maintainers and see if we can improve this for future users!
If you have any ideas of what you'd like to see added as hints to the readme / anything else for that exercise, feel free to open a PR for it too - we love having the community grow and raise these issues!
Hi @NobbZ, you raise a good point. I think that the only reason we pass
null is because that is what happens in the canonical data, but we could deviate (overloaded methods seem obvious here, but might be a more complex idea this early in the track).
static, one of our POLICIES is to prefer instance methods. I don't think this would simplify the exercise particularly, though maybe I am the wrong person to ask and we should seek a beginner's input.
Above, Lee has only expressed an issue with the README, something that we might add hints to. I'd be interested in seeing what the others thought here though :smile:
Mathclass IIRC, which doesn't get instantiated as well.
Hi @katmpatz!! That's great to hear - we always like to get new contributors :smile:
All of the issues should be unresolved. Not all of them require an entire exercise to be implemented, some will be small changes - this can often be a good starting point! At the moment, most of the issues are about updating some of the tests we have. There is a pretty large range of issues to pick up at the minute :smile:
If you would like to implement an exercise that isn't completed in Java yet, the list can be found here. If you let one of the Java team know, we will be more than happy to open an issue and assign you to it, so no-one else will take the same thing!
Does that all make sense? I'm happy to discuss more questions any time :fireworks:
exercism configure 2>&1 | grep -- --apireturns blank