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

Replace "possibly \tcode{const}" with "possibly const" #6025

Merged
merged 1 commit into from Dec 16, 2022
Merged

Replace "possibly \tcode{const}" with "possibly const" #6025

merged 1 commit into from Dec 16, 2022

Conversation

tkoeppe
Copy link
Contributor

@tkoeppe tkoeppe commented Dec 16, 2022

The "const" here is not syntax, but just normal text. This is similar to "inline" and "public", which have previously been cleaned up similarly.

Fixes #117.

@tkoeppe
Replace "possibly \tcode{const}" with "possibly const"
1301d07 
The "const" here is not syntax, but just normal text.
This is similar to "inline" and "public", which have
previously been cleaned up similarly.
@tkoeppe
Copy link
Contributor Author

tkoeppe commented Dec 16, 2022

@jwakely, @jensmaurer, @zygoloid, @sdutoit ^^^

jensmaurer
jensmaurer approved these changes Dec 16, 2022
View reviewed changes
Copy link
Member

@jensmaurer jensmaurer left a comment

Choose a reason for hiding this comment

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

Consistency is good.

@tkoeppe tkoeppe merged commit 433fcd7 into cplusplus:main Dec 16, 2022
@tkoeppe tkoeppe deleted the noconst branch December 18, 2022 21:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@jensmaurer jensmaurer jensmaurer approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

"possibly const" vs "possibly \tcode{const}" vs "possibly \keyword{const}"
2 participants
@tkoeppe @jensmaurer