On Thu, Jan 15, 2026 at 9:35 PM Robert Engels <[email protected]> wrote:
> Not that the best software is designed by consensus but I appreciate the
> support Mike. I like Go. Nothing is perfect. It’s amazing they were able to
> add generics in a backwards compatible manner. But I long for a Go 2.0
> where they broke compatibility and fixed some critical errors that I
> suspect the core Go is well aware of.
>
This one could be fixed without breaking any existing code. For example, we
might say that, on the left side of a plain assignment, prefixing an
identifier with an @ sign means the identifier is being declared there, as
if by :=. The example above would become
@x , @err = method1()
if err !=nil {
...
}
@y , err = method2() // Using existing err, so not @err
if err !=nil {
...
}
I suspect this wouldn't fly... but if the problem bothers enough people
sufficiently, something could be done.
--
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 [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/golang-nuts/CAADvV_tzsZQH2HtwaZzAOZaPvY2xBWqizYnHWKvNiEcdc81iig%40mail.gmail.com.
