Draft
99 Problems, #5: reversing a list
33 of 234spencerwi
Loading description...
Lists
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.
This comment has been hidden.
This comment has been hidden.
The text given should be:
let rec reverse = (YOUR CODE HERE)
Duplicate: https://www.codewars.com/kata/esrever
Concept is the same but the description states
without using any built-in reverse functions.
plus the fact it's coded in two different and very new languages - I've never used F# or OCaml before.I think the author should actually give the credit to the source of this entire series https://ocaml.org/learn/tutorials/99problems.html though.
I didn't notice the other kata doesn't state that in the description but reversing functions are removed there. I like new languages too but I don't think it changes anything. There are translations, and translations to new languages are getting approved quickly, and katas with new translations appear in the top of the list.
@Unnamed: Please, don't take this personally. You're the first who came with "duplication comments" but as I know there are few others who could have done this.
Duplication Inquisition in action (lol) (I've expected these duplication comments :))
Yes, there are translations, but:
I have two translations which have been waiting for approval for 4 months
But they first need to be approved.
Don't forget that to create a translation, one actually has to solve the kata first. Why should one bother himself with solving a kata in JS, Python or whatever language if he only wants to create a F#, Haskell (or whatever) translation. And also, what if one knows one language? He shouldn't create a new kata because he doesn't know another language etc. (I've asked this already and got an answer but I still can't agree with this approach.)
Other thing is that one doesn't know if there's a published but not approved translation before he solves the kata...
The very last thing: I can't understand why people solve duplicate katas and then complain about duplication.
Regards,
suic
The "very last thing..." is easy to explain and surely you know it... 3 points for nothing and if it gets "Draft" nobody else can get;-)
Anyway, I don't mind if these issues get closed, it's just for those who come to approve to be aware.
@smile: I know. The solving part makes perfect sense :) But then why to complian about duplication. (This isn't a real question.) :) Normally, no action is taken when someone identifies a duplicate.
@Unnamed: I forgot to mention one positive side effect. These comments shows which duplicate one hasn't solved yet ergo even more easy points :)
All I wanted was to use the term "Duplication Inquisition" :) and pointing out the difficulties of translations. For me this debate is finished.
Regards,
suic
Duplicate katas do get handled, I've personally commented about duplicates on katas that have then been removed because of the obvious duplication. If you really want to create the same kata but in a different language you must use translations because multiple katas with the same specifications end up having the same languages translated for them making the second kata basically free points which is unjust because it is a duplication. If you really want to translate a kata you should go to the effort to solve it in the languages given. It's a great excuse to learn a new language one that no one should pass up, if that's too hard then forfit the kata and create a translation, duplicate katas are a problem because points are awarded unfairly and it is a problem that should probably be addressed more formaly. :)
I get
in OCaml (with any solution).
Thanks! I had a typo:
(fun_ ->
instead of(fun _ ->
, causing my lambda not to be seen as such.