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

Jump to bottom

types2: better error messages for specific operations with type parameters #47211

Open
griesemer opened this issue Jul 14, 2021 · 2 comments
Open

types2: better error messages for specific operations with type parameters #47211

griesemer opened this issue Jul 14, 2021 · 2 comments
Assignees
@griesemer
Labels
NeedsFix The path to resolution is known, but the work has not been done.
Milestone
Go1.21

Comments

@griesemer
Copy link
Contributor

This is a reminder issue to address the comments about better error messages in the following CLs:

CL 333709
CL 333712
CL 333713
CL 333729
CL 333770
@griesemer griesemer added the NeedsFix The path to resolution is known, but the work has not been done. label Jul 14, 2021
@griesemer griesemer added this to the Go1.18 milestone Jul 14, 2021
@griesemer griesemer self-assigned this Jul 14, 2021
@griesemer griesemer changed the title types2: better error messages for operations with type parameters types2: better error messages for specific operations with type parameters Jul 14, 2021
@griesemer
Copy link
Contributor Author

Too late for 1.18. Moving to 1.19.

@griesemer griesemer modified the milestones: Go1.18, Go1.19 Feb 11, 2022
@griesemer
Copy link
Contributor Author

Background: These CLs changed operations from working on ordinary types to working on type parameters. Depending on the type set, the operations may fail. Should provide clearer indication why they fail (which type in the type set got them to fail). Needs a bit of time.

Moving to 1.20.

@griesemer griesemer modified the milestones: Go1.19, Go1.20 Jun 24, 2022
@griesemer griesemer modified the milestones: Go1.20, Go1.21 Nov 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@griesemer griesemer

Labels
NeedsFix The path to resolution is known, but the work has not been done.
Projects
Release Status & Blockers (1.20)
Status: No status
Milestone
Go1.21
Development

No branches or pull requests
1 participant
@griesemer