Re:
well, I actually find it rather weird that you thought about "out of the array" as "walls" in the first place, considering the goal is to go out of that array.

The problem is not "out of the array". The problem is with "Note that the maze may not always be square or even rectangular."

Here is the issue
When one considers that the maze is not rectangular, this means that the later array elements (i.e. a row of the maze) may be shorter than the earlier ones. But the question remains, when that row is shorter than the others, does it imply that the skipped columns (the right most ones) are blank spaces or are they '#'s? That's what needs to be clarified.

Does this help?

i found it ambiguous too

well, I actually find it rather weird that you thought about "out of the array" as "walls" in the first place, considering the goal is to go out of that array.

Ah, because I believe the suggestion resolves an "issue". The issue is that the instructions are ambiguous.

Thanks. Fixed.

Typo in: The is considered cheating and is a very dishonorable thing to do! Note that
First word should be "This". Hope this is helpful!

Hi,

My suggestion...

So... Why not to use the "suggestion" flag, then?

Firstly, thank you for this great challenge. It was fun!

I believe the instructions should be clarified. Saying the maze does not have to be a rectangle is not clear. It could mean either that you should treat blank spaces (e.g. last two chars in the last row, which has 8 columns where the others had 10) as walls or that you should treat them as edges where you've succeeded in escaping. I interpret it the first way, which caused me some confusion. Effectively, the maze always is a rectangle, it's just not always given as such in the input data. You have to extrapolate it into a rectangle.

My suggestion would be to say something like, "The maze input is not always a rectangle. Any spaces not defined by the input should be treated as open spaces (not walls)."