I'm a fan of fixing the casing issues, but not too big of a fan of the other two. Mainly because it feels like those two proposals add syntactic sugar in order to achieve brevity. I do believe verbosity is one of the reasons I like Go so much. You spend most of the day thinking, not writing code. Making it easier to read and understand is a plus for me. Having more constructs does add to more confusion while reading IMHO.
I totally agree with verbosity being important in Go. I think the collect is my least favorite of the three, I personally don't mind the if err != nil pattern that much. I like the idea of interface literals though, I feel like needing my code to be separate from where I use it is a bit much.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I'm a fan of fixing the casing issues, but not too big of a fan of the other two. Mainly because it feels like those two proposals add syntactic sugar in order to achieve brevity. I do believe verbosity is one of the reasons I like Go so much. You spend most of the day thinking, not writing code. Making it easier to read and understand is a plus for me. Having more constructs does add to more confusion while reading IMHO.
I totally agree with verbosity being important in Go. I think the
collectis my least favorite of the three, I personally don't mind theif err != nilpattern that much. I like the idea of interface literals though, I feel like needing my code to be separate from where I use it is a bit much.