Skip to content
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

Open
hobovsky opened this issue Mar 12, 2023 · 6 comments
Open

Deduplicate - Find missing element #184

hobovsky opened this issue Mar 12, 2023 · 6 comments
Labels
discussion/deduplicate Discussion and vote what to do with duplicate kata

Comments

@hobovsky
Copy link
Contributor

From #39

  1. Return the Missing Element
  • 7kyu
  • input: array of numbers from 0-9 with one missing
  • Satisfaction: 94% with 9k completions
  • No pending issues
  • 10 languages + 2 pending translations, 4 unique
  • Published Nov 2013, author inactive
  1. Find the Missing Number
  • 7kyu
  • input: array of numbers from 0-100(inclusive) with one missing)
  • Satisfaction: 93% with 5k solutions
  • 1 pending issue
  • 10 languages + 3 pending translations, 5 unique
  • Published Oct 2016, author inactive
@hobovsky hobovsky converted this from a draft issue Mar 12, 2023
@hobovsky hobovsky moved this from Acknowledged to Discussing in Deduplication process Mar 12, 2023
@hobovsky
Copy link
Contributor Author

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?

@Blind4Basics
Copy link

keep 2, retire 1. The amount of work seems slightly lower with 2 (one less translation/one less unique)

@JohanWiltink
Copy link

JohanWiltink commented Mar 12, 2023

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.

@Blind4Basics
Copy link

solutions are not retired in any way. That's a non argument ;)

@4500zenja1
Copy link

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).

@ejini6969
Copy link

This one can be concluded too

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion/deduplicate Discussion and vote what to do with duplicate kata
Projects
Status: Discussing
Development

No branches or pull requests

5 participants