Tim Tiefenbach

Regarding `dplyr::select` the issue is caused by `tidyselect::eval_select`. I digged into this a little in this [SO answer](https://stackoverflow.com/a/67653948/9349302). Regarding `dplyr::mutate` I'm not sure if this is caused by {tidyselect}.

Just to add another example similar to the one in test-lmap.R: ``` r (l1 $a #> [1] 1 #> #> $b #> [1] "foo" ``` Lets assume we want to...

Apologies for splitting the original reprex into several pieces. Below is the code in one piece: ``` r # setup library(purrr) # example 1 # example function and input list...

For some context how I stumbled upon this odd behavior of `lmap_if`: I was translating {purrr} functions as for loops using the examples in the docs and in the test...

Thanks for looking into this! I'm not sure why your error message is 410, but from my experience the Twitter API yields weird and inappropriate error messages especially when the...

I think `fold` would be a great extension of {dplyover}, but a better name should be found given that {rsample} uses `vfold` and {furrr} has also a `fold` function. Then...

Thank you for your feedback! Unfortunately `over` and the other functions in the *over-across function family* don't work like that. `over` loops over a vector and creates a new column...

Thanks for your feedback and the suggestion to support `dplyr::mutate`'s `.keep` argument in `across2`. Without relying on {dplyr}'s internals, which I try to avoid, it might be a bit tricky....

It's a very nice idea to have support for dplyr's backends. I totally see adding this feature, but I guess it would require to first dive into the different backend...

One possible way to modify the loop to make it work would be to wrap the rewritten function in `eval(bquote())` and evaluate every input with `.()`. ``` # --- convert:...