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.

Sign up for GitHub

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

Jump to bottom

Inconsistent complexities for average/worst #2749

Closed
burblebee opened this issue Mar 7, 2019 · 1 comment · Fixed by #2921
Closed

Inconsistent complexities for average/worst #2749

burblebee opened this issue Mar 7, 2019 · 1 comment · Fixed by #2921
Assignees
@jensmaurer

Comments

@burblebee
Copy link
Contributor

We're inconsitent as to wether we do
Average case x. Worst case y.
vs
Average case x, worst case y.
when describing complexities in library tables.

In #2718, jensmaurer added:

I would even vouch for a semicolon here. Yes, please make that a separate editorial issue and put "decision-required" on it.
@burblebee burblebee mentioned this issue Mar 7, 2019
Merged
@burblebee burblebee added the decision-required A decision of the editorial group (or the Project Editor) is required. label Mar 7, 2019
@jensmaurer jensmaurer removed the decision-required A decision of the editorial group (or the Project Editor) is required. label Jun 5, 2019
@jensmaurer
Copy link
Member

jensmaurer commented Jun 5, 2019 •
edited

Editorial meeting: Go for comma, lowercase (which is also the majority of existing uses).

@jensmaurer jensmaurer self-assigned this Jun 6, 2019
@jensmaurer jensmaurer mentioned this issue Jun 6, 2019
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jensmaurer jensmaurer

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[unord.req] Consistently use 'Average case x, worst case y.' jensmaurer/draft
2 participants
@burblebee @jensmaurer