You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This maze is simpler with only two rooms. The first needs a key that checks if the arrays contain the equal contents. The second needs a key that is more flexible about checking equality of numbers.
For example:
a ; => #[13 23]
b ; => #[13 23.0]
(key-arrays a b) ; => NIL
(key-arrays-loosely a b) ; => T
because a permissive equality predicate will not consider numeric type when comparing the contents of an array.
would it make sense for the readme or the tests be updated to mirror each other?
The text was updated successfully, but these errors were encountered:
At Exercism we use our Community Forum, not GitHub issues, as the primary place for discussion. That allows maintainers and contributors from across Exercism's ecosystem to discuss your problems/ideas/suggestions without them having to subscribe to hundreds of repositories.
This issue will be automatically closed. Please use this link to copy your GitHub Issue into a new topic on the forum, where we look forward to chatting with you!
If you're interested in learning more about this auto-responder, please read this blog post.
@driftsignal I updated the test data and instructions to hopefully remove the possible confusion. Please review #803 and let me know if you think it corrects this problem.
the equality test for maze of arrays appears to test for identity.
key-comparison-test.lisp line 115-118:
the readme suggests internal comparison:
would it make sense for the readme or the tests be updated to mirror each other?
The text was updated successfully, but these errors were encountered: