Hi everyone, The proposal was closed about a week ago with the conclusion that: "There was further discussion, but no change in consensus on this particular proposal."
First of all, let me begin that I am always humbled by the wisdom and passion of the Go community and that this whole process has taught me a lot. Since most Go2 proposals fail to be accepted, I am not surprised by the outcome. As I said in my experience report, my main goal was to raise awareness of the problem addressed in the proposal, and not realistically solve it in one Go. As I have put a lot of effort into writing the experience report and later, the proposal, I would really appreciate to hear some feedback about what the community thinks, and if a core dev team can share a bit more specifics, this will allow me to learn and improve. With this introduction over, I have 3 simple question. You DON'T need to answer them all. Any answer will be appreciated. 1. What did you think about the problem the proposal addresses? Do you think its significant? 2. Do you think this is a problem that Go should solve in a future version? 3. Lastly, what are the strengths and weaknesses of the proposal? Many thanks. -- 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/87d3ea16-9f3c-4b09-8ccb-89bdf4bd5803n%40googlegroups.com.
