If Go is to be standardized, it needs to be as late as possible in the
development of Go 1. My observations of being involved with some standards is
that the participants view it as an opportunity to change or add to whatever is
being standardized. Unless the standard was simply a true codification of the
existing Go 1 language (e.g., the existing Go compiler is strictly conformant)
I think it would do harm to the language. As others have mentioned, it would
be best to do this once Go 1 pretty much stops being developed. We certainly
don't want a standards organization to essentially define Go++.
-Paul
On 10/11/18, 10:58 PM, "golang-nuts@googlegroups.com on behalf of Beoran"
<golang-nuts@googlegroups.com on behalf of beo...@gmail.com> wrote:
So no matter if I say yes or no, both ways are bad? I think is not a very
fair way to argue.
Anyway, with the Ruby standard you can do either. The Ruby standard defines
that there are strictly conforming Ruby processors, which implement the
standard and conforming Ruby processors which may have any number of additional
implementation defined extensions, alternate syntax and language features.
After the standard was written, mruby was implemented to be a strictly
conforming Ruby processor, which doesn't influence or hold back the development
of the other Ruby implementations at all.
And all other Ruby implementations can be considered confirming, which is
worth millions of $$$ to Ruby developers. The organizations and governments I
mentioned tend to have deep pockets, and the Ruby standard enables us to gain
approval from said bureaucrats. So, we can now use Ruby for these well funded
projects, since now it is an international standard.
So actually, because the Ruby standard was carefully written to enable
this, it has been win/win for Ruby developers. You can use a strictly
conforming mruby if you like or need to, or use any other Ruby implementations
as conforming ones and please the bureaucrats.
I consider that we should do the same for Go. When done carefully it will
also be a win/win.
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
