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

inconsistent use of periods versus hyphens in [defns] #5225

Closed
zygoloid opened this issue Jan 21, 2022 · 0 comments · Fixed by #5227
Closed

inconsistent use of periods versus hyphens in [defns] #5225

zygoloid opened this issue Jan 21, 2022 · 0 comments · Fixed by #5227
Assignees

Comments

@zygoloid
Copy link
Member

In some labels in defns, hyphens in a term translate into hyphens in the label:

  • [defns.direct-non-list-init]
  • [defns.expression-equivalent]

In other labels, they become periods:

  • [defns.prog.def.spec]
  • [defns.prog.def.type]

Finally we have some cases where the noun is dropped when abbreviating to form the label; in these cases we seem to consistently use a period rather than a hyphen:

  • [defns.cond.supp]
  • [defns.impl.defined]
  • [defns.locale.specific]
  • [defns.well.formed]

(That last category might make sense, because English style guides often say to omit the hyphens in compound adjectives when used without a noun, but we don't do that in the standard, eg: "the behavior is implementation-defined" not "the behavior is implementation defined".)

Some consistency here would be nice. Maybe the first two examples above should change from hyphens to periods?

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 a pull request may close this issue.

2 participants