debug mode such to ignore memory buffer provided to the linker to store its
outputs in them.

mq is nice, but sometimes it screws up where the patch gets applied...

later harder ( we would need to check if two scan have the same
mode_instance class or the same instance when we decide to merge??)

So if tall c code is already compiled, we don't take it!

'Fix test in DebugMode. We don't implement optimization with the borrow flag on output in DebugMode.'

I've also make the documentation more clear on the actual behaviour of
n_steps.

incorrect 'n_steps' to scan.

steps, scan does that number of steps or raises an error ( i.e. it does not
check the length of the sequences and pick the largest number of steps). It
makes things more optimizable, in terms of scan mergings. It is also
logical, if you provided the number of steps, you do expect those number of
steps to be executed. I might need to check documentation to make sure it is
in sync with scan.

calls the linker directly).