I'm thinking about the following task: one table with current stock and maximum stock capacity for each product, and then the purchases and sales tables. User should make a sql report with current stock after each purchase/sale, and actions taken for each purchase/sale -> approved or rejected. A purchase is rejected when stock is full and a sale is rejected when stock is empty. Do you think such kata is too close to the current kata you are drafting? If not, I'll have a go at authoring such kata.

I hope author goes for (2) here, which was the intended way (looking at author comments in a previous discussion). This would be a challenging task in SQL.

Very interesting, you could easily make an entire series of kata's on this subject, each with different expected behavior for sales when nothing is in stock ;)

don't have much time today :/. Putting kata into draft and will carefully work with all issues when have time (and re-check my solution because looks that it has issues)...Very interesting problem

Fixed by fork.

Indeed, there was just "primes" in JS. Changed it to semiprimes

I wrote the JS translation and used the exact same batch suite names as in Python. The ~ stands for prime and almost-primes.

If i am not wrong, that section called "~64bit semiprimes". Number is semiprime if it has two distinct prime factors.

Unless you would do some tests where you don't get ALL values, but only take(x) and you put some exceptions or sleeps further on the sequence. But do we want to push it that far ..

Of course it works. Because testing is necessarily finite.

If you think setting Infinity to 100 000 won't come back to bite you some day, have at it. I think you actually know better.

Design decision to use the same integer type for all fractions in this kata series.

Added

There's a conjecture about that.