I'm talking about the example from the https://hexdocs.pm/gleam_otp/gleam/otp/actor.html documentation page. I don't understand how is Pop message allowed to be used as the second argument to the call function when it's a type, and not a function. How can I make it work when the message type has more arguments than one?
#Why does actor.call work with a type when it's expecting a function?
leaden drift
cobalt crown
Pop isn't a type, it's a value constructor, aka a function
Message(Int) is a type and the value Pop(12) belongs to that type
leaden drift
Oh, OK, so every value constructor is basically a function. So Pop(Subject(Something)) is like a fn (Subject(Something)) { Pop(Subject(Something)) }, right?
Is it possible to somehow curry that function, so if it has more arguments I can still use it this way?
Something like Pop(Subject(...), SomeData), so I can still use it the same way as in the example.
stoic token
you can use the _ shorthand, like Pop(_, SomeData), or a lambda if it's more complex/nested than that
leaden drift
Oh, right, I remember that from the tour now. Thanks.
For reference: https://tour.gleam.run/functions/function-captures/
Only one capture is allowed, right?
stoic token
yes, but process.call can only take an arity-1 function anyway