Skip to content

Conversation

@Quuxplusone
Copy link
Contributor

Now that many sections use "annotation" to mean a specific core-language construct, we should avoid using "annotation" to mean anything but that construct, i.e. stop using it to mean "code comment." (There will be an NB comment to this effect.)

Drive-by hyphenate "freestanding-deleted function". Not all freestanding-deleted functions are freestanding functions, and not all freestanding-deleted functions are deleted functions; hyphenating helps the reader understand that this is a term of art that cannot meaningfully be broken down into its component notions.

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.

The rest looks good.

…notation"; hyphenate "freestanding-deleted"

Now that many sections use "annotation" to mean a specific core-language
construct, we should avoid using "annotation" to mean anything but that construct,
i.e. stop using it to mean "code comment." (There will be an NB comment to this effect.)

Drive-by hyphenate "freestanding-deleted function". Not all freestanding-deleted
functions are freestanding functions, and not all freestanding-deleted functions
are deleted functions; hyphenating helps the reader understand that this is a
term of art that cannot meaningfully be broken down into its component notions.
@tkoeppe tkoeppe added the needs rebase The pull request needs a git rebase to resolve merge conflicts. label Nov 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

needs rebase The pull request needs a git rebase to resolve merge conflicts.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants