I would also like to hear from somebody about a real world use-case. I don't pretend to be proficient in this realm of functional programming, but I would be very surprised if this is valuable in a language like Go that can and does hold state. That said, this is very cool and I would love to be proven wrong.
On Friday, June 17, 2016 at 7:34:04 AM UTC-7, Evan Digby wrote: > > Currying is translating the evaluation of a function with multiple > arguments into evaluating a sequence of functions with one argument. Not > sure how this doesn't qualify, even if a closure was used to accomplish > this. > > As for the value, at the very least there is the same value as using > closures in general. The rest (why converting to single argument functions > for pure Currying was necessary) would have to be use-case specific. The > example given doesn't speak to why it's valuable. > > I would be curious to understand the value by exploring more real-world > use-cases myself! > > -- 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.
