Solution and sample tests being editable are normal. I would have to see a screenshot to see what's going on, but it looks good from my end when I "train again"
Sorry for being nitpicky, but if you add a space between the closing ) and the opening { in the function signature of the initial code, I will approve it. Like this:
Is there a way to know if m exists or not(a Boolean)?
There are certain conditions that imply that there is no m. If you look carefully at the sample tests, those conditions might become clear. I can't really say more without adding a spoiler.
.
Solution and sample tests being editable are normal. I would have to see a screenshot to see what's going on, but it looks good from my end when I "train again"
.
Approved at 6-kyu
Sorry for being nitpicky, but if you add a space between the closing
)
and the opening{
in the function signature of the initial code, I will approve it. Like this:There isn't an exact duplicate but the task lacks novelty and is basically string manipulation without much puzzle-thinking or in-depth analysis ...
Your solution modifies the input list
pattern_l
, which is then used by the author solution. That should be a kata issue, I'll raise it rnyou are using global variables, don't do that. they keep their values between function calls
OP solved it, closing
Reading the description should make the condition for m being undefined very obvious.
There are certain conditions that imply that there is no m. If you look carefully at the sample tests, those conditions might become clear. I can't really say more without adding a spoiler.
tbh, upon appropriate reflection, I agree that full disclosure with explicit specs is generally the best approach
Indeed. I think that's very very justified for a number with thousands of digits.
NOTE: m can be very very LARGE
so, that's TWO (2)
very
sAdded: "Where necessary, the way of handling big integers appropriate to the language should be used."
Loading more items...