You need to sign in or sign up before continuing.×
6 kyu
Northwest and Southeast corners
68 of 148aweleshetu
Loading description...
Mathematics
Fundamentals
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.
python new test framework is required. updated in this fork
Forked & Approved
Honor points go to t̷h̴e̵ v̸̤̠͎͕͇͈̼͋̂͝ò̸̺̻̩̤̘̻̅̎͂̈́͆̄͆̃̔̀͜͝ị̷̍̎̓͠͝d̴̢̨̛̯̤̥͉̥̠͍̋̌̄̉͐͜ͅ
The user can modify the input.
Fixed
The description is still difficult to understand. I thought the idea was to find the farthest points from the center by calculating distances, but it's much simpler.
Python example test case, random tests and description fixed.
@anter69, nice job!
The Python example test is not valid.
really ? i have tested it again and it works as supposed. can you paste your test flagged as spoiler ? so i can see where it went wrong.
done
Nice idea. Fairly simple.
I'd recommend expanding on your description, however.
Thanks for all those suggestions, i will put 'em on it.
I think the tests should be fixed so that they don't throw sytax errors. The goal should be writing the code, and not fixing the tests.
They didn't throw any errors for me. Maybe they've been fixed, or my code didn't trigger them somehow...
what were those syntax errors you experienced ? They were no test cases set to check syntax errors.
done
Your testing is vulnerable to input modification (see here).
You should give user a copy of the input array he can clobber all he wants, or call the reference solution before calling the user solution with the input.
Nice catch, though it seems more an issue than a suggestion. This should've been fixed before the kata got approved.
TBH, I never thought this kata would get approved. Given it's initial bad rating. But
Johan
's suggestion is now implemented, which invalidates the cheat solution provided. soThAnKs Johan
:)This comment has been hidden.
If it makes any difference, I do appreciate your attention to detail when reviewing katas. I have no qualms about having legitimate criticisms directed my way regarding my code, so if you see a bug with any katas that I publish, please do raise an issue.
I fixed the example test - it was missing a
)
. (That can't be tested from the kata editor page, only from the trainer - it's easy to overlook. And with all the nested round, square, angle and squiggly brackets it's all too easy to get one wrong.)Your reference solution has a potential bug - if any quadrant is not in the input coordinates some compass direction variable will be
[]
and some coordinate of the final answer will beundefined
.And the correct spelling of
cornor
would becorner
. But I did not dare fix that, for fear of messing up the whole kata. Wouldn't want that; it is functionally correct as it is.nice one! i will correct those :)
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
done