-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deduplicate - Find missing element #184
Comments
I have no good candidate here. Kata 1. is older and has more completions, but looks close to trivial. But still, range of 2. does not really make any difference. Maintenance-wise they seem to be similar. Any ideas? |
keep 2, retire 1. The amount of work seems slightly lower with 2 (one less translation/one less unique) |
They're functionally identical. (2) is as trivial as (1). Keep 1, retire 2. The newer one should not have been approved, as a duplicate, and no need to retire more solutions. |
solutions are not retired in any way. That's a non argument ;) |
Since these katas are almost identical to each other with the same approach, I suggest to keep the oldest one (namely, 1) and retire 2 with transferring all existing unique languages prior that (these are, Clojure, COBOL, C++, Elixir). |
This one can be concluded too |
From #39
The text was updated successfully, but these errors were encountered: