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

go/types, types2: be consistent about the words 'parameterized' vs 'generic' in error messages and documentation #49593

findleyr opened this issue Nov 15, 2021 · 0 comments


Copy link

@findleyr findleyr commented Nov 15, 2021

Reminder issue: we have some error messages that use the word 'generic', when we've been preferring 'parameterized' in most cases. We also have some instances of the word 'generic' in documentation.

We should decide on exactly when to use each word, and do an audit for consistent usage. FWIW, I sometimes prefer 'generic' because it is shorter than 'parameterized' and not liable to be confused by normal function parameters. But most important to be consistent.

Assigning the Go1.18 milestone, but this is not a release blocker.

CC @griesemer

@findleyr findleyr added this to the Go1.18 milestone Nov 15, 2021
@griesemer griesemer self-assigned this Nov 15, 2021
@findleyr findleyr self-assigned this Nov 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants