RE: [go-nuts] Is Go too strict for nesting function callings?

2017-01-31 Thread John Souvestre
Interesting! Thanks. John John Souvestre - New Orleans LA From: golang-nuts@googlegroups.com [mailto:golang-nuts@googlegroups.com] On Behalf Of Jonas August Sent: 2017 January 30, Mon 04:25 To: golang-nuts Subject: Re: [go-nuts] Is Go too strict for nesting function callings

Re: [go-nuts] Is Go too strict for nesting function callings?

2017-01-30 Thread Jonas August
On Wednesday, January 25, 2017 at 5:48:44 PM UTC-5, John Souvestre wrote: > > Does this mean that there is no way to call this function? > >func h(func()(int, bool)) {} > No, you can call it by passing in a function value f itself instead of its result values f(). Using f in the top

RE: [go-nuts] Is Go too strict for nesting function callings?

2017-01-25 Thread Dave Cheney
I see it that the g(f()) special case is just that,a special case, added to make common use case less tedious. It's not an invitation to extend its rubbery semantics to all classes of function call. -- You received this message because you are subscribed to the Google Groups "golang-nuts"

RE: [go-nuts] Is Go too strict for nesting function callings?

2017-01-25 Thread John Souvestre
ct: Re: [go-nuts] Is Go too strict for nesting function callings? On Wed, Jan 25, 2017 at 5:05 PM, John Souvestre <jo...@souvestre.com > wrote: > > Thanks! I see both the limitation and the exception. > > Other than implementation complexity, is there a reason for

Re: [go-nuts] Is Go too strict for nesting function callings?

2017-01-25 Thread Dave Cheney
tion, but removing a limitation > and the exception due to it. :) > > John > > John Souvestre - New Orleans LA > > > -Original Message- > From: Ian Lance Taylor [mailto:ia...@golang.org ] > Sent: 2017 January 25, Wed 19:18 > To: John Souvestre &g

RE: [go-nuts] Is Go too strict for nesting function callings?

2017-01-25 Thread John Souvestre
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,

Re: [go-nuts] Is Go too strict for nesting function callings?

2017-01-25 Thread Ian Lance Taylor
On Wed, Jan 25, 2017 at 5:05 PM, John Souvestre 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 >

RE: [go-nuts] Is Go too strict for nesting function callings?

2017-01-25 Thread John Souvestre
Orleans LA -Original Message- From: Caleb Spare [mailto:cesp...@gmail.com] Sent: 2017 January 25, Wed 18:46 To: John Souvestre Cc: golang-nuts Subject: Re: [go-nuts] Is Go too strict for nesting function callings? https://golang.org/ref/spec#Calls Look for "As a special

Re: [go-nuts] Is Go too strict for nesting function callings?

2017-01-25 Thread Caleb Spare
@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

RE: [go-nuts] Is Go too strict for nesting function callings?

2017-01-25 Thread John Souvestre
groups.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

RE: [go-nuts] Is Go too strict for nesting function callings?

2017-01-25 Thread Dave Cheney
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,

RE: [go-nuts] Is Go too strict for nesting function callings?

2017-01-25 Thread John Souvestre
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:06 To: golang-nuts Subject: RE: [go-nuts] Is Go too strict for nesting function callings? I think you're tal

RE: [go-nuts] Is Go too strict for nesting function callings?

2017-01-25 Thread Dave Cheney
I think you're talking about a different example to TL. -- 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

RE: [go-nuts] Is Go too strict for nesting function callings?

2017-01-25 Thread John Souvestre
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