Re: [go-nuts] Language Feature Proposal: define

2016-08-24 Thread tommy xiao
yes, the type is you want. 2016-08-21 19:16 GMT+08:00 Henry : > Uh oh. You're right. Thanks for reminding me. Somehow I missed that. > > -- > You received this message because you are subscribed to the Google Groups > "golang-nuts" group. > To unsubscribe from this group and stop receiving emails

Re: [go-nuts] Language Feature Proposal: define

2016-08-21 Thread Henry
Uh oh. You're right. Thanks for reminding me. Somehow I missed that. -- 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. Fo

Re: [go-nuts] Language Feature Proposal: define

2016-08-21 Thread Jan Mercl
On Sun, Aug 21, 2016, 13:05 Henry wrote: > Hi, > > I think some aspects of Go language are rather verbose to the extent > that they hurts readability. For instance, let's take closures. The > following is a bit hard to read: > > func MyFunction(rows *sql.Rows, parser func(raw *sql.Rows) ([]MyData

[go-nuts] Language Feature Proposal: define

2016-08-21 Thread Henry
Hi, I think some aspects of Go language are rather verbose to the extent that they hurts readability. For instance, let's take closures. The following is a bit hard to read: func MyFunction(rows *sql.Rows, parser func(raw *sql.Rows) ([]MyData, error )) ([]MyData,error){ ... } It would be ni