Done !

I refactored the description and improved the tests so this should not be a problem. Marking resolved.

approved!

i've updated the description to be more clear.

Thanks! CoffeeScript looks like an interesting language :) Approved!

Oooops : bummer !

Well done ! :))

Actually, even looking at maps, pathes were not so easy to find.
One reason is description is not clear enough about keys ("K") :

• first I thought I should take them all
• but some are not reachable

I think it's necessary to clarify this point in description :
"collect the maximum possible number of keys, -> /!\ important: some keys are impossible to collect"

It also could be helpfull to show the visited maps (eg a console.log like I used in my "solution" :

"<pre>"+map.replace(/ /g,"_").split("\n").map(row=>row.split("").join(' ')).join("\n")+"</pre>"

)

Happy coding!

Thank you, I will look at that. @bojidar-bg if there is nothing else, could you please mark this suggestion as resolved, Thanks :)

Ah! Editing glitch. I changed the name of the variable, and didn't fix all the descriptions. Please try to keep your temper, though; it was an honest mistake.

@matt c: Maybe you want to take part in this discussion.

I know it does, but when you convert the code to a string it changes it to the old function so evaluating on a string is the only way to tell if someone uses an arrow function or not... If you don't agree try it yourself otherwise could you please mark this suggestion as resolved? thanks :)