Hi Dave.
I'm trying to understand this. What is the rule?
Does this mean that there is no way to call this function?
func h(func()(int, bool)) {}
Is there any disadvantage to not allowing the "syntactic sugar" to work in all
cases?
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 15:42
To: golang-nuts
Subject: [go-nuts] Is Go too strict for nesting function callings?
The confusion comes, like most cases in go, where a little syntactic sugar has
been added to make the common case more appealing, but has the side effect of
making the less common case more jarring.
g1(f())
Is th exception to the rule. By _not_ requiring the caller to capture each
value from evaluating f() by hand before calling g1.
--
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.
