Issues like these are not usually tracked in the issue tracker. It is just for bugs and proposals to the language.

But I am not sure where should they be tracked. @bradfitz ?

Yes, you are right, but I didn't quite see where too raise this suggestion. Maybe on the mailing list in stead?

or for developing safety critical applications using certain international standards

Note that according to the Go license:

I would not advise its use in safety-critical applications.

It is rare that the compiler builder gives any warranty, although there are some safety certified C compilers. But for similar certified Go compilers to be developed, we need an official standard first.

Even if the compiler is not certified, you can still use it if you validate it yourself. This implementation of go has extensive unit tests which simplifies such validation a lot.

I know of some safety critical software that is implemented in C and compiled with GCC. As a language, Go is far safer than that, and that is why we need a standard, to be able to get away from C for safety applications.

This should be discussed on golang-nuts, not the issue tracker. Thanks.

Ok, I will. Sorry for the noise.