Skip to content

Unhyphenate "potentially-evaluated"#8939

Open
frederick-vs-ja wants to merge 1 commit intocplusplus:mainfrom
frederick-vs-ja:unhyphante-potentially-evaluated
Open

Unhyphenate "potentially-evaluated"#8939
frederick-vs-ja wants to merge 1 commit intocplusplus:mainfrom
frederick-vs-ja:unhyphante-potentially-evaluated

Conversation

@frederick-vs-ja
Copy link
Copy Markdown
Contributor

Currently we define unhyphenated "potentially evaluated" in [basic.def.odr]/3 for expressions and conversions, but also define hyphenated "potentially-evaluated subexpressions" in [intro.execution]/4.

It's probably better to use a single form, and the hyphen shouldn't b used for compounds modifying a noun if an adverb ending in "ly" is used.

Fixes #8937.

Currently we define unhyphenated "_potentially evaluated_" in
[basic.def.odr]/3 for expressions and conversions, but also define
hyphenated "_potentially-evaluated subexpressions_" in
[intro.execution]/4.

It's probably better to use a single form, and the hyphen shouldn't b
used for compounds modifying a noun if an adverb ending in "ly" is used.
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.

"potentially evaluated expression" vs "potentially-evaluated subexpression"

1 participant