At least, in C++, could use a callable that someone would modify (function pointer or std::function<> of some sort).
Nice idea for a hakathon, IMHO bad idea for this codesite. Note: Had the ability to edit: should have delete :-(
It was my intention to not give the implementation of tryEscape() so the users have to find the implementation by themselves by dumping the memory.
I will add tags soon.
At least, in C++, could use a callable that someone would modify (function pointer or std::function<> of some sort).
Nice idea for a hakathon, IMHO bad idea for this codesite.
Note: Had the ability to edit: should have delete :-(
Neat, could you try to cheese again pls
No it is not.
Other katas are also split because the puzzle type is the same but the solution is different.
This kata uses a unique (I hope) solution.
Take these two for example:
https://www.codewars.com/kata/5510caecaacf801f820002ac
https://www.codewars.com/kata/54bd6b4c956834c9870001a1
meaning it's a duplicate?
I added tags
Should be fixed now.
Can you please validate.
And the solution which I did is my intended solution.
Other katas do the same thing like https://www.codewars.com/kata/54bd6b4c956834c9870001a1/
It was my intention to not give the implementation of tryEscape() so the users have to find the implementation by themselves by dumping the memory.
I will add tags soon.
Also, you gotta fix the simplest cheese like this
In fact, author solution is doing the equivalent of cheating, so this is not a good idea for a kata either.
With zero information given (not even the implementation of
tryEscape, or any tags, or anything?), this kata is not a good puzzle.