-
-
Notifications
You must be signed in to change notification settings - Fork 46.8k
Merge sort best & average case O(n)? #340
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
Comments
it's O(n log n ) only. |
#342 I changed the readme and created a pull request |
It is O(n*log(n)) for best, average and worst case. |
Yes! It should be O(n*log(n)) for every case i.e. best case, average case, worst case. |
Are you pointing out that there should be a "" between n and log(n)? In readme file Merge, Quick and Shell is also using one space as multiplication instead of "*". Thats why I also used it that way in the PR. |
@hasangokdag No. In the master, best & average are |
Hi @sfdye , @hasangokdag has corrected precisely what you are saying in his commit. Look at his commit: ce3e678 |
@piyush-kgp Yeah I am aware of the PR. It should get high priority as this simple typo could fail someone's interview. |
Yes. you are right. Just noticed that this thread is 9 days old. Apologies. |
Thanks @hasangokdag |
Finally this is merged. Cheers 👍 |
https://github.com/TheAlgorithms/Python/blob/master/README.md#merge
Shouldn't it be O(n log n).
The Java repo is correct though:
https://github.com/TheAlgorithms/Java#merge
The text was updated successfully, but these errors were encountered: