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

cmd/compile: type-check cmd/compile/internal/syntax nodes directly #24780

Open
griesemer opened this issue Apr 9, 2018 · 3 comments

Comments

Projects
None yet
3 participants
@griesemer
Copy link
Contributor

commented Apr 9, 2018

We should move type-checking to operate directly on the new syntax nodes. Placeholder issue.

Set for Go1.12 so it stays on the radar. Unclear yet if that is a realistic goal.

@rasky

This comment has been minimized.

Copy link
Member

commented Apr 9, 2018

Is this something where new contributors can help? Is it sort of a long-term incremental task where you can lead by example with a few CLs and then people can follow the lead and submit more?

@griesemer

This comment has been minimized.

Copy link
Contributor Author

commented Apr 9, 2018

@rasky Sorry, this is definitively not a task for new contributors. If we're going to do this we need to do this in the Go Team, with dedicated engineering. Thanks.

@griesemer griesemer modified the milestones: Go1.12, Go1.13 Oct 24, 2018

@griesemer

This comment has been minimized.

Copy link
Contributor Author

commented Oct 24, 2018

Moving to 1.13.

@griesemer griesemer modified the milestones: Go1.13, Go1.14 May 6, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.