Then I'm still confused. Where is this inconsistency / limitation /
non-orthogonal "syntactic sugar" defined? I'm trying to understand why it
exists if perhaps it isn't necessary.
John
John Souvestre - New Orleans LA
-----Original Message-----
From: golang-nuts@googlegroups.com [mailto:golang-nuts@googlegroups.com] On
Behalf Of Dave Cheney
Sent: 2017 January 25, Wed 18:30
To: golang-nuts
Subject: RE: [go-nuts] Is Go too strict for nesting function callings?
It was just a turn of phrase, it's not a real rule.
--
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.
--
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.
