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

stop using teletype font for constexpr function #559

Closed
zygoloid opened this issue Nov 4, 2015 · 3 comments
Closed

stop using teletype font for constexpr function #559

zygoloid opened this issue Nov 4, 2015 · 3 comments

Comments

@zygoloid
Copy link
Member

zygoloid commented Nov 4, 2015

The term "constexpr function" is currently formatted as "constexpr function". This is misleading, since such functions need not use the constexpr specifier. Instead, we should only use the teletype font when referring to the keyword, matching how we treat the terms "inline function" and "function declared with the inline specifier".

@sigfpe
Copy link

sigfpe commented Nov 4, 2015

Makes sense.-------- Original message --------From: Richard Smith notifications@github.com Date: 11/4/2015 2:00 PM (GMT-08:00) To: cplusplus/draft draft@noreply.github.com Subject: [draft] stop using teletype font for constexpr function (#559)
The term "constexpr function" is currently formatted as "constexpr function". This is misleading, since such functions need not use the constexpr specifier. Instead, we should only use the teletype font when referring to the keyword, matching how we treat the terms "inline function" and "function declared with the inline specifier".


Reply to this email directly or view it on GitHub.

@tkoeppe
Copy link
Contributor

tkoeppe commented Nov 14, 2015

What's the desired replacement? Just "constexpr function" without typographic distinctions? Or a real term, like "constant-expression function"?

@jensmaurer
Copy link
Member

Duplicate of #825.

@jensmaurer jensmaurer removed the decision-required A decision of the editorial group (or the Project Editor) is required. label Nov 29, 2016
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

No branches or pull requests

4 participants