Skip to content

Correct bogosort's best case runtime #186

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

Merged
merged 1 commit into from
Jul 1, 2018
Merged

Correct bogosort's best case runtime #186

merged 1 commit into from
Jul 1, 2018

Conversation

Ivan-Johnson
Copy link
Contributor

Bogosort's best case runtime is not constant, because even if the array
is already sorted, it still has to perform Θ(n) operations to verify
that each of the n elements are in order.

Bogosort's best case runtime is not constant, because even if the array
is already sorted, it still has to perform Θ(n) operations to verify
that each of the n elements are in order.
@Butt4cak3 Butt4cak3 added the Chapter Edit This changes the archive's chapters. (md files are edited.) label Jun 30, 2018
Copy link
Member

@leios leios left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Correct, thanks for the change! For some reason, I thought the "checking" was not part of the algorithmic complexity, but it obviously is.

@leios leios merged commit 5710e2b into algorithm-archivists:master Jul 1, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Chapter Edit This changes the archive's chapters. (md files are edited.)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants