> The design draft was put up for discussion for months before it became a formal proposal. It was not new.
There is always a "discussion", most people (as well as I) will look only at the final version of proposal, if and when they have time. And what's the point of having formal proposals if you don't respect that process? Once you published, please notify everyone and give them time to come back with critics. Or just do what you do, but don't tell me or anyone that there is any "community" behind, "decade of discussion" and all that stuff. > The formal proposal (https://golang.org/issue/43651) got 1784 thumbs up and 123 thumbs down (and ten "confused"). Yes, there were critics. But I think it is fair to say that the proposal has far more supporters than critics. LOL. You LOCKED that issue (including emojis!). You locked because Russ or whoever is responsible for the process in the company, was afraid that it will be like with "try" proposal. So please don't. And are you saying that "consensus" is how many emojis "up", "down" or "confused" were collected? You know that it's pretty easy to cheat with that system right? вт, 16 мар. 2021 г. в 01:03, Ian Lance Taylor <i...@golang.org>: > On Mon, Mar 15, 2021 at 5:08 AM Space A. <reexist...@gmail.com> wrote: > > > > > For example, the multiple proposals that flowed out of > > > https://go.googlesource.com/proposal/+/master/design/go2draft-error-handling-overview.md > . > > None of them have been adopted. > > > > I remember what was happening to "try" error handling proposal. It was > withdrawn only because of active resistance by the community. > > > > And what's happened to a new "generics" proposal, it also got a lot of > critics but was "accepted" in less than a month after formal publication on > github. As Russ said "No change in consensus". What does it mean? Who are > these people who can change the consensus? How was it measured? A few days > after Russ locked it, so nobody can even say a word against it if they > wanted. So it looks very much that company management learned from "try" > proposal. > > The design draft was put up for discussion for months before it became > a formal proposal. It was not new. > > The formal proposal (https://golang.org/issue/43651) got 1784 thumbs > up and 123 thumbs down (and ten "confused"). Yes, there were critics. > But I think it is fair to say that the proposal has far more > supporters than critics. > > The "no change in consensus" comment refers to the discussion after > the proposal was moved to "likely accept" status: > https://github.com/golang/go/issues/43651#issuecomment-772744198. > After it was marked as "likely accept", there was no change to the > consensus that it should be accepted. (Note that the "likely accept" > comment got 60 thumbs up and 0 thumbs down (and one "confused").) > > None of this is anything like the "try" proposal > (https://golang.org/issue/32437), which had 318 thumbs up and 794 > thumbs down (and 132 "confused"). > > Ian > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/CADKwOTc%2BmjiJOia%3DGt%3D63xAdPmbRSo5RE9XJaNxcp2g38bXoxA%40mail.gmail.com.
