Beta
Shifting base N numbers
17 of 18smckaysmalley
Loading description...
Algorithms
Algebra
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.
the dummy JS version is still there, tho
=> you need to delete it from the edit panel
Ah. Thanks. I thought you were requesting JS translation.
This comment has been hidden.
Thanks for the feedback!
I can use your ref methods for the random tests -> use procs instead of methods for the ref solution
You don't want this solution to pass: cheese
question is: can you discover them without "cheating"? Because procs come with their own problmes as well (not here, but in general)
mmhm good question, I was able to find them by first solving it the normal way, but I do remember some docs (on CW ?) recommending procs over methods to guard against users using the ref solution
You most probably mean this: https://docs.codewars.com/languages/ruby/authoring#reference-solution but I'm not a Ruby person so I'm not familiar with actual implications of one approach or another.
yep that's the one
yeah, the ruby situation will stay a... situation as long as the files will be merged together.
Refined a little further.
letfor additional scopingVerified this solution no longer passes.
This comment has been hidden.
because lambda suffers from the same vulnerability as method, while proc does not: CHEESE