← Back to context

Comment by OldfieldFund

5 days ago

I invoke them :]

Shame we can't use `cast`, that's already being used for types. And `conjure` probably only works for object constructors.

  • Erlang/Elixir use "cast" method name when sending messages to their GenServer actor processes.

    • There are two terms.

      * call - to send and await a reply * cast - to send and not await a reply

  • let's use conjure for method interactions and reify as a special case when that method is a constructor. the more this sounds like medieval alchemy the more I can get behind it, and I've already got misbehaving daemons

The functional peeps even `apply` them.

  • I've never been quite sure when I'm applying data to a function, or applying a function to some data

    • This tripped me up last week when I was reading Futamura’s paper on partial evaluation (i .e., Futamura projections). I’m not used to the “apply” terminology for functions, even though I learned the lambda calculus in grad school over a decade ago.

    • to my mind the function has always been the definition of the process and the data what that process, well, applies to. so you apply the function to the data and get an output.

Same here, but I will say "a function call", not "a function invocation".

Invoking X sounds deliciously alchymistic, by the way.