We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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?
to your account
[edit: By setting type information directly in syntax nodes rather than storing in types2 maps, we should be able to recover some of the compiler speed loss of Go 1.18.]
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.
The text was updated successfully, but these errors were encountered:
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?
Sorry, something went wrong.
@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.
Moving to 1.13.
Change https://go.dev/cl/396917 mentions this issue: cmd/compile: store type information directly in syntax tree
cmd/compile: store type information directly in syntax tree
Some progress has been made on this: syntax expression nodes now can be augmented directly.
Moving to 1.22.
No branches or pull requests