We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I agree the coding is more interesting, but I have a hard time accepting assert!(triangle.is_equilateral()); assert!(!triangle.is_isosceles());
The text was updated successfully, but these errors were encountered:
Given that exercism/problem-specifications#379 has been discussed and exercism/problem-specifications#424 has been merged as a result, we should resolve this issue by complying with the suite.
Re-visiting #206 would be a quick win in this area, though it may be worth it to rewrite the test suite follow the structure of the new JSON file.
Sorry, something went wrong.
Agreeing with @petertseng here. I think if you have an approach that you want to suggest, updating the official JSON file is the way to go.
No branches or pull requests
I agree the coding is more interesting, but I have a hard time accepting
assert!(triangle.is_equilateral());
assert!(!triangle.is_isosceles());
The text was updated successfully, but these errors were encountered: