Hi Ian.
OK, I understand now.
Btw - I wasn't proposing adding an exception, but removing a limitation and the
exception due to it. :)
John
John Souvestre - New Orleans LA
-----Original Message-----
From: Ian Lance Taylor [mailto:i...@golang.org]
Sent: 2017 January 25, Wed 19:18
To: John Souvestre
Cc: golang-nuts
Subject: Re: [go-nuts] Is Go too strict for nesting function callings?
On Wed, Jan 25, 2017 at 5:05 PM, John Souvestre <j...@souvestre.com> wrote:
>
> Thanks! I see both the limitation and the exception.
>
> Other than implementation complexity, is there a reason for the limitation of
> single-valued expressions? Is there some fundamental problem with allowing
> multi-valued expressions that I'm missing?
It's potentially confusing when used with variadic functions. If we
extend past function calls, it's potentially confusing when used with
multi-valued assignment statements. It's hard to make fully general
while avoiding confusion, and specific uses don't seem to arise often
enough in practice to justify adding more exceptions to the language.
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.
For more options, visit https://groups.google.com/d/optout.
