I have been trying to solve this problem with Java and ran into this same problem. I currently have 220 passing tests and 10 failures. All 10 failures are related to this flaw. I am not able to see the tests' code, so I cannot see what is actually being checked. I tried giving my exception classes with messages that matched the expected unclean termination exception messages, but they are apparently not checked. I thought it might be expecting it in the OutputStream objects, except I discovered that every test of this category passes a null OutputStream.

I am inclined to conclude that this problem's Java test suite was broken at some point in the past and never fixed. The fact that I am replying to a two-year-old comment that was never addressed is incredibly discouraging.

fixed

ikr

Nice! I actually did the exact same thing for traversing the AST. I guess my slow time came from elswere or Java just being slower than C.

yes

115,370 completions say otherwise. Can you elaborate which test case you think is wrong?

You cannot go from 75 to 77
you can only move down a row or down a row and right one index

Java version expects you to throw an error for unclean termination AND output result?? How is that even possible?
Expected exception for unclean termination caught: java.lang.IllegalArgumentException <-- it expected me to throw a exception, which I did
unclean termination expected:1 but was: null <-- and then still wanted me to return 1?

It would be great if some example InputStreams could be provided in the sample tests
It would also be great if it could be clarified that A) Output stream is NOT OPTIONAL B) Example Tests dont pass a Output stream as a parameter but Full test suite does and C) the outputstream you are given is always null

FIRST 1KYU KATA GG
Also just curious how fast other peoples solutions were, even though this isnt a performance kata, my code generated horribly inefficient instructions imo.
Time: 2534 ms

But then people hardcode