You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When should it fail, vs fall back to apply? Should it emit a warning? How could this be customized?
How could singledispatch be used with CallTreeVisitor? Can we demo using a vector function (e.g. row_number, n, cumsum)
Could type annotations be leveraged here? E.g. automatically wrap a vector function based on it's return type, or some other function annotation.
How can a user audit the behaviors siuba will take before executing e.g. a grouped mutate?
Premortem: pretend we're looking back 3 months from now, and the process is not working--what are the main reasons that is (e.g. user perspective, dev, perspective, person who has been programming for 1 day perspective)?
The text was updated successfully, but these errors were encountered:
When should it fail, vs fall back to apply? Should it emit a warning? How could this be customized?
How could singledispatch be used with CallTreeVisitor? Can we demo using a vector function (e.g.
row_number
,n
,cumsum
)Could type annotations be leveraged here? E.g. automatically wrap a vector function based on it's return type, or some other function annotation.
How can a user audit the behaviors siuba will take before executing e.g. a grouped mutate?
Premortem: pretend we're looking back 3 months from now, and the process is not working--what are the main reasons that is (e.g. user perspective, dev, perspective, person who has been programming for 1 day perspective)?
The text was updated successfully, but these errors were encountered: