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, x/tools: help tool authors support the new go/types.Alias node #67263

Open
4 tasks
findleyr opened this issue May 8, 2024 · 1 comment
Open
4 tasks
Labels
early-in-cycle A change that should be done early in the 3 month dev cycle. NeedsFix The path to resolution is known, but the work has not been done.
Milestone

Comments

@findleyr
Copy link
Contributor

findleyr commented May 8, 2024

Following up on #46477 (comment), this umbrella issue tracks additional actions we can take to help tool authors support the new go/types.Alias node. We've learned a lot from our work on #64581, and should share this knowledge:

(anyone is welcome to suggest more actions we can take)

CC @adonovan @timothy-king

@findleyr findleyr added this to the Go1.24 milestone May 8, 2024
@findleyr findleyr added the early-in-cycle A change that should be done early in the 3 month dev cycle. label May 8, 2024
@cherrymui cherrymui added the NeedsFix The path to resolution is known, but the work has not been done. label May 10, 2024
@gopherbot
Copy link
Contributor

This issue is currently labeled as early-in-cycle for Go 1.24.
That time is now, so a friendly reminder to look at it again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
early-in-cycle A change that should be done early in the 3 month dev cycle. NeedsFix The path to resolution is known, but the work has not been done.
Projects
None yet
Development

No branches or pull requests

3 participants