4 kyu
Hypercube Lists
75Wintro
Loading description...
Algorithms
Lists
Recursion
View
This comment has been reported as {{ abuseKindText }}.
Show
This comment has been hidden. You can view it now .
This comment can not be viewed.
- |
- Reply
- Edit
- View Solution
- Expand 1 Reply Expand {{ comments?.length }} replies
- Collapse
- Spoiler
- Remove
- Remove comment & replies
- Report
{{ fetchSolutionsError }}
-
-
Your rendered github-flavored markdown will appear here.
-
Label this discussion...
-
No Label
Keep the comment unlabeled if none of the below applies.
-
Issue
Use the issue label when reporting problems with the kata.
Be sure to explain the problem clearly and include the steps to reproduce. -
Suggestion
Use the suggestion label if you have feedback on how this kata can be improved.
-
Question
Use the question label if you have questions and/or need help solving the kata.
Don't forget to mention the language you're using, and mark as having spoiler if you include your solution.
-
No Label
- Cancel
Commenting is not allowed on this discussion
You cannot view this solution
There is no solution to show
Please sign in or sign up to leave a comment.
It should be clearly stated in the description the input should not be modified. From the current description, several users interpreted that an inline modification of the list was required, or at least possible.
Really cool kata, it should be much more popular. The description seems scary, but the task itself is not that hard. Give it a try!
great, just solved it, thanks for the motivational speech ;)
Do not modify the nested list in your implementation or you won't pass the test ;)
It took me some time to understand that given nested list should not be modified in the process. I think a clear mentioning of such requirement should be provided in the task section.
i don´t really know how to start please help
Maybe just start with simpler kata? Not an issue, in any case.
cheers
I don't understand this error message input should not be changed: [[5, 2, [0, 0, 0, 0], [0, 0, 0, 0]], 1] should equal [[5, 2, [], []], 1] Does this message mean that [[5, 2, [], []], 1] should be a hypercube? it's strange...
My code passes all tests except "input should not be changed" tests.
Basically means you messed with the inputs somehow in your function and it wasn't the same as before. Try avoiding it by copying or something
Test case with given array
[[], [], [], []]
returns the following error:Am I misunderstanding this? The pattern looks like "If you see a lone number available in a slot, duplicate it appropriately, but if there is nothing there, add 0s", yet somehow your algo wants 3s here.
don;t add zeros, add provided
growing_value
(which is 3 in this case)approved.
Your kata is really interesting, but presents A LOT of problems, for now...:
Description / solution setup:
default
(well, it's said in the description, yes, but since there are no sample tests with that, the information is only shown "with 5 words" in the whole (huge) descirption)aN function
somewhere near the end, for example)You'll have to transform an input nested list into an hypercube list, which is a special kind of nested list where each level must have the very same size, the nesting going to the same depth in each branch too
(You'll surely need to reformulate the last part about the depth: I cannot find a way to translate correctly what I have in mind in english). And only then give the example and the formal definitions if you want.Sample tests: you HAVE to put in there:
Test cases:
If you resolve all of these problems, your kata will become a really solid one. You put a lot of effort in the test suite, already, it's a good one. Just make it perfect! ;)
updated
please look again
(using python)
Is it an issue or did I do something wrong if I get
even when I just submit
Fixed. Please try again.
Thanks, but I still get the same error.
You must be using python 3.6. I will change the question to reflect that.
Well, actually I didn't pick the version and it's 3.4.3 as default. I just try
again and make sure py3.4.3 is chosen, but it's still the same
typing
used to be in the Python 3.4 version because the previous Python 3.4 is a mess (it's kind of an amalgam of 3.4 and 3.6). Now that the new runner is out and 3.4/3.6 are separated properly, you won't be able to usetyping
in 3.4 anymore ;-)This comment has been hidden.
Fixed and publishing. Thank you!
Umm.. You have not completely solved this issue
I could have sworn I did a find and replace on that.
Fixed now (I hope!)