Skip to content

Use correct article in help message for conversion or cast #77278

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 4 commits into from
Oct 19, 2020

Conversation

camelid
Copy link
Member

@camelid camelid commented Sep 27, 2020

Before it always used an; now it uses the correct article for the type.

@rust-highfive
Copy link
Contributor

r? @estebank

(rust_highfive has picked a reviewer for you, use r? to override)

@rust-highfive rust-highfive added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Sep 27, 2020
@camelid camelid added A-diagnostics Area: Messages for errors, warnings, and lints C-enhancement Category: An issue proposing an enhancement or a PR with one. labels Sep 27, 2020
Before it always used `an`; now it uses the correct article for the type.
@camelid camelid force-pushed the use-correct-article branch from 186893d to 549f861 Compare September 27, 2020 20:51
Also added missing backtick in "you can cast" message.
@camelid
Copy link
Member Author

camelid commented Sep 29, 2020

The wording for this kind of bothers me:

let msg = format!("{} and panic if the converted value wouldn't fit", msg);

I think it might sound better as "if the converted value doesn't fit". I think "wouldn't" to me makes it sound like it's a compile-time thing, but it's not. Can I change it?

EDIT: I changed it. Let me know if I should change it back.

@camelid
Copy link
Member Author

camelid commented Oct 2, 2020

@estebank Could you re-review this sometime soon? It would be nice to get this in before the release. But if you're not able to soon, I understand!

@jyn514 jyn514 added the T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. label Oct 11, 2020
It felt too harsh to estebank and others to ICE even though it's
technically a mistake to show a `TyKind::Error`.
@Dylan-DPC-zz
Copy link

looks good to me

@bors r=estebank rollup

@bors
Copy link
Collaborator

bors commented Oct 19, 2020

📌 Commit 3eab21e has been approved by estebank

@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 Oct 19, 2020
@bors
Copy link
Collaborator

bors commented Oct 19, 2020

⌛ Testing commit 3eab21e with merge 78307d8...

@bors
Copy link
Collaborator

bors commented Oct 19, 2020

☀️ Test successful - checks-actions, checks-azure
Approved by: estebank
Pushing 78307d8 to master...

@bors bors added the merged-by-bors This PR was explicitly merged by bors. label Oct 19, 2020
@bors bors merged commit 78307d8 into rust-lang:master Oct 19, 2020
@rustbot rustbot added this to the 1.49.0 milestone Oct 19, 2020
@camelid camelid deleted the use-correct-article branch October 19, 2020 04:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-diagnostics Area: Messages for errors, warnings, and lints C-enhancement Category: An issue proposing an enhancement or a PR with one. merged-by-bors This PR was explicitly merged by bors. S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants