Fixed.

Same, it's tragic that the testing framework's It macro makes including <range/v3/all.hpp> impossible. Any brevity you are able to achieve is offset by the gazillion lines of import above it :(

Agreed, but I also think that even with those utilities, this task isn't trivial to do correctly. Of course, if you copy everything and turn things into lvalues, it is. But it took me 30 minutes to put together a solution that keeps value categories intact. I assumed there would be tests for that, and also the caching, but apparently not

Thank you for reply + couple of keywords) Im trying to find purpose for "kumite" thing thus bothering people around.. that the spirit, i guess
gotta have some fun with llvm intermediates x)

C-style cast makes it 98% close. XD
Your idea with ranges sounds great.

That was my approach too

This kata needs a complete overhaul. Better input/output format, test verification and random test generator. Author has left the building and I ain't touching the current C++ and C# code. Let's retire this and make the 8x8 variation the author hinted at in the description.

Changed to array of 2 vectors of integers.

This is a great kata, but I agree, the function prototype is not good.

I don't know exactly what it could be, but I can tell you where my performance problem was. After I wrote a working solution I had a constant timeout on tests. The problem I had was that I chose the wrong algorithm for comparing > and <, he was too ineffective. I implemented one algorithm for this and then just swapped if I needed to take >:

    ...
    def lt(self, id1: int, id2: int) -> int:
        ...

    def gt(self, id1: int, id2: int) -> int:
        return self.lt(id2, id1)
    ...

And yes, if I have the < algorithm implemented now, that means I had > before. If anything, I was looking at the implementation from here. Try implementing < if you currently have > implemented.

My guess is that you have an intermittent infinite BF loop (e.g. due to some non-zeroed vars). Try out the online BF debugger to diagnose: https://esolangpark.vercel.app/ide/brainfuck

If I understand your question correctly. It has already been discussed here.

Good point!

I am out of town for a few weeks, but I will fix it when I get back.