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

Fix cannot usage in time.rs #123815

Merged
merged 1 commit into from
May 3, 2024
Merged

Fix cannot usage in time.rs #123815

merged 1 commit into from
May 3, 2024

Conversation

trueb2
Copy link
Contributor

@trueb2 trueb2 commented Apr 11, 2024

Fix a small grammar error in usage of cannot in time.rs errors

@rustbot
Copy link
Collaborator

rustbot commented Apr 11, 2024

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @workingjubilee (or someone else) some time within the next two weeks.

Please see the contribution instructions for more information. Namely, in order to ensure the minimum review times lag, PR authors and assigned reviewers should ensure that the review label (S-waiting-on-review and S-waiting-on-author) stays updated, invoking these commands when appropriate:

  • @rustbot author: the review is finished, PR author should check the comments and take action accordingly
  • @rustbot review: the author is ready for a review, this PR will be queued again in the reviewer's queue

@rustbot rustbot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-libs Relevant to the library team, which will review and decide on the PR/issue. labels Apr 11, 2024
@workingjubilee
Copy link
Member

@trueb2 This is not ungrammatical?

@trueb2
Copy link
Contributor Author

trueb2 commented Apr 11, 2024

@workingjubilee
Copy link
Member

It says preferred, not standard, and that

Both cannot and can not are perfectly fine,

And I would prefer to not introduce noise into the history over such a whitespace-only diff with no stronger reasoning.

@workingjubilee
Copy link
Member

@trueb2 There are other, more glaring and unquestionable, grammatical issues in this file. I can accept this if it either

  • does a more thorough pass or
  • constrains itself only to changing the error messages, which are user-facing.

I do not desire to set a trend of encouraging people to closely review the comments, viewed only by implementers, for rigid adherence to prescriptivist notions of English grammar. We have contributors from all over the world, and it would be an untenable barrier to set holding people to strict adherence to Chicago MoS or AP Style in comments, and we do not document which stylebook we would prefer people to adhere to, either.

@trueb2
Copy link
Contributor Author

trueb2 commented Apr 12, 2024

I only opened the PR because the grammar was wrong in a panic message. Code comments don't affect end users, so I figured I was being nice by fixing the cannot usage everywhere. I assumed it was noise to fix all of the grammar.

@workingjubilee
Copy link
Member

I am mostly concerned about precedent.

Squash please?

@workingjubilee
Copy link
Member

Ah!

@bors r+ rollup

@bors
Copy link
Contributor

bors commented May 3, 2024

📌 Commit 3ad0618 has been approved by workingjubilee

It is now in the queue for this repository.

@bors bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels May 3, 2024
workingjubilee added a commit to workingjubilee/rustc that referenced this pull request May 3, 2024
Fix cannot usage in time.rs

Fix a small grammar error in usage of cannot in time.rs errors
matthiaskrgr added a commit to matthiaskrgr/rust that referenced this pull request May 3, 2024
Fix cannot usage in time.rs

Fix a small grammar error in usage of cannot in time.rs errors
bors added a commit to rust-lang-ci/rust that referenced this pull request May 3, 2024
…iaskrgr

Rollup of 7 pull requests

Successful merges:

 - rust-lang#122492 (Implement ptr_as_ref_unchecked)
 - rust-lang#123815 (Fix cannot usage in time.rs)
 - rust-lang#124059 (default_alloc_error_hook: explain difference to default __rdl_oom in alloc)
 - rust-lang#124510 (Add raw identifier in a typo suggestion)
 - rust-lang#124555 (coverage: Clean up creation of MC/DC condition bitmaps)
 - rust-lang#124593 (Describe and use CStr literals in CStr and CString docs)
 - rust-lang#124630 (CI: remove `env-x86_64-apple-tests` YAML anchor)

r? `@ghost`
`@rustbot` modify labels: rollup
@bors bors merged commit 4b913a2 into rust-lang:master May 3, 2024
10 checks passed
@rustbot rustbot added this to the 1.80.0 milestone May 3, 2024
rust-timer added a commit to rust-lang-ci/rust that referenced this pull request May 3, 2024
Rollup merge of rust-lang#123815 - trueb2:patch-1, r=workingjubilee

Fix cannot usage in time.rs

Fix a small grammar error in usage of cannot in time.rs errors
@trueb2 trueb2 deleted the patch-1 branch May 17, 2024 16:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. T-libs Relevant to the library team, which will review and decide on the PR/issue.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants