Thank you, Jesper, that's very interesting.
On Sunday, June 19, 2016 at 8:15:13 AM UTC-7, Jesper Louis Andersen wrote:
>
>
> On Sat, Jun 18, 2016 at 5:32 AM, Tyler Compton > wrote:
>
>> I don't pretend to be proficient in this realm of functional programming,
>> but I would be very surprised if
On Sat, Jun 18, 2016 at 5:32 AM, Tyler Compton wrote:
> 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.
In functional languages, it is often used as a way to "conf
Note that Go's reflect package is powerful enough to implement
currying directly, though you do have to convert back to the expected
type in order to call the function.
https://play.golang.org/p/2ukRfHGnlT
Ian
--
You received this message because you are subscribed to the Google Groups
"golang
I played around tonight trying to come up with a better way, but instead I
came up with 2 decidedly worse ways (particularly considering
readability/maintenance is the primary concern of the question). I think
they're novel enough to share!
https://play.golang.org/p/w9YxsEFlF8
1) Original
2)
Go allows functions to have multiple arguments. The upside is currying is much
less necessary in languages like Go. The downside is combining one-argument
functions to make new one-argument functions is syntactically more cumbersome.
--
You received this message because you are subscribed to
Note the _excessive_ caveat. Used with some restraint I think it is a very
powerful construct.
On Fri, Jun 17, 2016, 03:42 adonovan via golang-nuts <
golang-nuts@googlegroups.com> wrote:
> On Thursday, 16 June 2016 18:00:43 UTC-4, Zauberkraut wrote:
>>
>> would an extended usage of this paradigm
