> apparently has some reason for being unwilling to accept the resulting mixed-license state. As someone who writes a lot of Go, I can understand the reason fo

> apparently has some reason for being unwilling to accept the resulting mixed-license state. As someone who writes a lot of Go, I can understand the reason for this. If I reuse a function from the standard library, I don't want to have to check which headers happen to pertain to that. I'd much rather know that all Go code is covered by the same license, and therefore the same header. For what it's worth, all Go code so far is under the same license[0]. Even the Go-specific parts of gccgo are under the same license as gc (though when distributed with gccgo, the combined package is distributed under the GPL). [0] http://golang.org http://golang.org lists these as the only exceptions to the BSD licensing for code and CC-BY licensing for non-code, which basically just means the obvious Google brand-specific stuff. https://developers.google.com/site-policies#restrictions https://developers.google.com/site-policies#restrictions