-
-
Notifications
You must be signed in to change notification settings - Fork 82
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
binary: improve tests for invalid numbers #111
Comments
The test suite doesn't cover these cases. One wrinkle. A submission might use the standard |
These new requirements will make it more complicated than simply using |
@verdammelt is that a bad thing? The original reason I added this was for newbie programmers to actually have to figure out how binary numbers work. |
I think it's also good for newbies to understand and use standard tools. I often see (and write) other iterations that implement the exercise more literally. We're also discussing it here: #107 |
There are other exercises that assume binary and would be good to use the standard tools for (secret handshake, I think, does this. Also maybe allergies, though I think maybe that's just bitwise, so the inputs are decimal but you're expected to think about them in binary). |
@kytrinyx good timing - i was literally (and I do mean literally) about to work on this issue. How did you know? |
Hah! That's a delightful coincidence. I've been catching up on email for three days straight, basically, and just accidentally got to this one. |
Decided to go ahead and push these changes anyway. Not sure how long getting |
Yeah, good call. It could be a while. |
We should have separate tests for:
If the test suite for binary has test cases that cover these edge cases, this issue can safely be closed.
See exercism/problem-specifications#95
The text was updated successfully, but these errors were encountered: