2 name: Language Change Proposals
3 about: Changes to the language
4 title: "proposal: Go 2: "
5 labels: Proposal Go2 LanguageChange
9 Our process for evaluating language changes can be found here:
10 https://go.googlesource.com/proposal/+/refs/heads/master#language-changes
15 - **Would you consider yourself a novice, intermediate, or experienced Go programmer?**
16 - **What other languages do you have experience with?**
20 - **Has this idea, or one like it, been proposed before?**
21 - **If so, how does this proposal differ?**
22 - **Does this affect error handling?**
23 - **If so, how does this differ from previous error handling proposals?**
24 - **Is this about generics?**
25 - **If so, how does this relate to the accepted design and other generics proposals?**
29 - **What is the proposed change?**
30 - **Who does this proposal help, and why?**
31 - **Please describe as precisely as possible the change to the language.**
32 - **What would change in the language spec?**
33 - **Please also describe the change informally, as in a class teaching Go.**
34 - **Is this change backward compatible?**
35 - Breaking the Go 1 compatibility guarantee is a large cost and requires a large benefit.
36 Show example code before and after the change.
39 - **Orthogonality: how does this change interact or overlap with existing features?**
40 - **Is the goal of this change a performance improvement?**
41 - **If so, what quantifiable improvement should we expect?**
42 - **How would we measure it?**
46 - **Would this change make Go easier or harder to learn, and why?**
47 - **What is the cost of this proposal? (Every language change has a cost).**
48 - **How many tools (such as vet, gopls, gofmt, goimports, etc.) would be affected?**
49 - **What is the compile time cost?**
50 - **What is the run time cost?**
51 - **Can you describe a possible implementation?**
52 - **Do you have a prototype? (This is not required.)**