Closed epatters closed 5 years ago
When recording a flow graph, *args and **kwargs arguments should be "expanded" as part of binding a function call to a function signature.
For example, one function that is currently broken is numpy's meshgrid, which has signature:
meshgrid
np.meshgrid(*xi, **kwargs)
Currently, the call np.meshgrid(x, y, copy=True) is bound as
np.meshgrid(x, y, copy=True)
xi=(x, y), kwargs={'copy': True}
Under our programming model, the call should be bound as something like
xi__0=x, xi__1=y, copy=True
When recording a flow graph, *args and **kwargs arguments should be "expanded" as part of binding a function call to a function signature.
For example, one function that is currently broken is numpy's
meshgrid
, which has signature:Currently, the call
np.meshgrid(x, y, copy=True)
is bound asUnder our programming model, the call should be bound as something like