Now let's create a kata for B... oh, wait

( JS )

Random tests runtimes vary wildly. Try to generate more consistently distributed sizes.

I got different results in my local IDE and on Codewars using the same inputs and code. Did I overlook something here?

It might be a good idea to change the expected output from bad values of n from empty collections to None/null/Option(I think?) in Python/JS/Java for future maintainability reasons. Should be possible to preserve old solutions as well.

If we need to return two sets of equal sum, wouldn't it be more appropriate to return the two sets as, well, sets instead of lists?

Duplicate of https://www.codewars.com/kata/59c919326bddd238e9000103

I find the naming of arguments in C# utterly confusing. The name length does not seem, at least to me, to be a good complement of width. The "length" and "width" seem to overlap in meaning, and I am not sure if "length" applies to rectangular matrices at all. I would suggest renaming length to width. With current setup, it's difficult to tell what argument relates to what dimension of the output matrix.

Why do you create "invalid" test cases? Just replace the currentValue by something different than 0 or 1 should suffice, no?

A duplicate to https://www.codewars.com/kata/5715508de1bf8174c1001832 (though that kata is extremely lenient on performance requirements).

Random test cases immediately have large number of inputs. This is very annoying to debug.

1. Duplicate.

2. Sample / actual testcase: Missing testcase/solution import.
   eg:

import codewars_test as test
from solution import process_digit_queries