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
This is not as trivial as I thought because as_mapper() also takes the dots, and we need to be careful to evaluate spliced arguments only once. So for now we'll just have to rely on the mapped function to support tidy dots.
That was my feeling as well. One workaround for effectively making map_*() comprehend dots-splicing would be for partial() to comprehend dots-splicing (cf. #457). But I'm not sure whether that'd be a practical alternative (how many users would think to do that?), not to mention the added verbosity.
Some functions support dots-splicing, e.g.,
while others do not, e.g.,
Should dots-splicing behavior be more consistent across purrr?
(I presume this might already be under consideration for tidyverse packages, generally. Just flagging it for the record ... )
The text was updated successfully, but these errors were encountered: