On Sun, Jun 14, 2020 at 5:25 PM Tom Limoncelli <t...@whatexit.org> wrote:
>
> On Thu, Jun 4, 2020 at 3:34 PM Ian Lance Taylor <i...@golang.org> wrote:
> >
> > On Thu, Jun 4, 2020 at 8:43 AM <lgod...@gmail.com> wrote:
> > >
> > > ?? Why not a cleaner syntax e.g. x = some_func () #{ } .. symbol #
> > > arbitrarily chosen
> >
> > Besides what other people have said, it may be of interest to glance
> > through
> > https://github.com/golang/go/issues?q=is%3Aissue+label%3Aerror-handling
>
> I assert that 80% of the annoyance that people feel is the number of
> lines required to handle errors, not the syntax. Thus, a large
> segment of the community would stop caring about this if we modified
> gofmt, not the go language.
They possibly would stop. But Another part of Go programmer, who
prefer explicit and easily visible, distinct flow control constructs,
would probably start complaining. (I'm in that camp.)
IOW, it's not possible to please everyone. Status quo has the lowest
cost of any such changes.
--
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/CAA40n-XrsbcQtUA4SHsnYN4jM7dHQ-GEn7ZH%3DmoGVofpxXWdHg%40mail.gmail.com.
