Already updated. To see the change, copy your code somewhere, click reset in the Kata trainer, paste your code back and re-try.
reset
I see. Thanks!
Edit: I've just realized that the description didn't cover that spaces can be absent when it doesn't introduce ambiguity. Will update test cases.
Original post: Is it really a parsing failure? I don't think so. It's a valid Lisp expression.
I got the following error. If this one is intented to catch parsing failure, should the expected value be Nothing?
expected: Just (I32 100) but got: Nothing
PS. I'm stuck at this kata for a while. So I did a little cheating using unsafePerformIO.
How is that ill-formed? Could you provide a better one? Test cases are intented for catch edge cases.
This comment is hidden because it contains spoiler information about the solution
Loading collection data...
Already updated. To see the change, copy your code somewhere, click
reset
in the Kata trainer, paste your code back and re-try.I see. Thanks!
Edit: I've just realized that the description didn't cover that spaces can be absent when it doesn't introduce ambiguity.
Will update test cases.
Original post:
Is it really a parsing failure? I don't think so. It's a valid Lisp expression.
I got the following error. If this one is intented to catch parsing failure, should the expected value be Nothing?
expected: Just (I32 100)
but got: Nothing
PS. I'm stuck at this kata for a while. So I did a little cheating using unsafePerformIO.
How is that ill-formed? Could you provide a better one? Test cases are intented for catch edge cases.
This comment is hidden because it contains spoiler information about the solution