I am checking correct ordering in the tests. I think that ordering in the output here indeed is not the focus of the logic being tested, but rather a way to validate correctness in assertions. If a query logically guarantees correct representation without explicit ordering, I believe it should be accepted.
BTW, brilliant solution, Twilight_Sun :) Like in Ukraine we are joking, "solution of the son of his mother's friend" :D
I would argue it depends on whether the ordering is an intended part of the challenge, or just a way to make sure your results are in the correct order for the assertion to work. I think it's the latter here. So if you manage to pass without explicitly ordering, good for you, no?
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
should be fixed, please reset trainer and try again, or you will have a hard time reaching 2 dan in js ;)
Fixed in all languages.
Fixed. TY for your contribution.
Interesting.. let me look into this. Thanks for finding it.
I am checking correct ordering in the tests. I think that ordering in the output here indeed is not the focus of the logic being tested, but rather a way to validate correctness in assertions. If a query logically guarantees correct representation without explicit ordering, I believe it should be accepted.
BTW, brilliant solution, Twilight_Sun :) Like in Ukraine we are joking, "solution of the son of his mother's friend" :D
I would argue it depends on whether the ordering is an intended part of the challenge, or just a way to make sure your results are in the correct order for the assertion to work. I think it's the latter here. So if you manage to pass without explicitly ordering, good for you, no?
yes
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.
Loading more items...