On Thu, Feb 12, 2015 at 7:01 AM, Keean Schupke <[email protected]> wrote:
> On 12 Feb 2015 14:57, "Jonathan S. Shapiro" <[email protected]> wrote: > > > > What you say is only correct if the procedure being applied can be > statically resolved. But in (say) _map_, the arity of the passed function > must be inferred from the body of the _map_ implementation. > > > > If map is in the same module, you have the body definition. If it is in a > different module you should have the type signature. > Good. So let us assume that map is *not* in the same module, and that I have the kind of type signature you prefer, which does not encode arity. How do I call _map_, since I nothing in this picture tells me its required argument passing convention? shap
_______________________________________________ bitc-dev mailing list [email protected] http://www.coyotos.org/mailman/listinfo/bitc-dev
