Skip to content

Use singlequotes in the typechecker error messages too, to distinguish code and English #1385

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
Dec 28, 2011

Conversation

kud1ing
Copy link

@kud1ing kud1ing commented Dec 25, 2011

Please correct if i quoted too much.

@brson
Copy link
Contributor

brson commented Dec 26, 2011

Don't we use backquotes for this type of thing, per #437 (not that I'm crazy about backquotes)?

@kud1ing
Copy link
Author

kud1ing commented Dec 26, 2011

That issue states: "but single quotes would work too" :)

I've seen single quotes in the frontend, i tried to be consistent with that
As long as we use any kind of quotes, that's fine with me.

Maybe we should write a macro or function to be consistent and flexible?
This could be based on "ty_to_str()" but i am not sure of its purpose and use.

@graydon
Copy link
Contributor

graydon commented Dec 28, 2011

I'm fine with single quotes, the few error messages that ever need to be specific about reporting char literals can be careful about it, and I don't expect we're likely to have error messages reporting full interpolated expressions (those can be, and often are, huge).

graydon added a commit that referenced this pull request Dec 28, 2011
Use singlequotes in the typechecker error messages too, to distinguish code and English
@graydon graydon merged commit f2c88c1 into rust-lang:master Dec 28, 2011
graydon added a commit that referenced this pull request Dec 28, 2011
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants