@@ -454,6 +454,34 @@ <h3 id="atomic_maps">
454
454
map access.
455
455
</ p >
456
456
457
+ < h3 id ="language_changes ">
458
+ Will you accept my language change?</ h3 >
459
+
460
+ < p >
461
+ People often suggest improvements to the language—the
462
+ < a href ="http://groups.google.com/group/golang-nuts "> mailing list</ a >
463
+ contains a rich history of such discussions—but very few of these changes have
464
+ been accepted.
465
+ </ p >
466
+
467
+ < p >
468
+ Although Go is an open source project, the language and libraries are protected
469
+ by a< a href ="/doc/go1compat.html "> compatibility promise</ a > that prevents
470
+ changes that break existing programs.
471
+ If your proposal violates the Go 1 specification we cannot even entertain the
472
+ idea, regardless of its merit.
473
+ A future major release of Go may be incompatible with Go 1, but we're not ready
474
+ to start talking about what that might be.
475
+ </ p >
476
+
477
+ < p >
478
+ Even if your proposal is compatible with the Go 1 spec, it may be
479
+ not be in the spirit of Go's design goals.
480
+ The article< i > < a href ="http://talks.golang.org/2012/splash.article "> Go
481
+ at Google: Language Design in the Service of Software Engineering</ a > </ i >
482
+ explains Go's origins and the motivation behind its design.
483
+ </ p >
484
+
457
485
< h2 id ="types "> Types</ h2 >
458
486
459
487
< h3 id ="Is_Go_an_object-oriented_language ">