Davis Vaughan

See also https://twitter.com/drob/status/1563198515626770432?s=20&t=iTFWSCPNOGWalIrpXHx2qg

We gave a serious attempt at this in #6313 for dplyr 1.1.0, but ultimately decided not to add it in that release. We aren't convinced that it is an operation...

I think the problem is that: ```r df |> filter(if_any(everything(), ~ .x == cur_column())) ``` tries to expand the `if_any()` call to: ```r df |> filter(x == cur_column() | y...

We might need some advice from @lionel- here I guess it is a little unfortunate that `cur_column()` is the _only_ helper where this issue would arise, as its the only...

We've also discussed letting `cur_data()` have a `cols` argument, or `...`, for this purpose. And possibly a `groups = TRUE/FALSE` argument to replace `cur_data_all()`

We should probably work towards deprecating `cur_data()` and `cur_data_all()` in favor of `pick()` too

Yea and `.cols` would continue to work, like: ```r if (missing(.cols)) { lifecycle::deprecate_warn("1.1.0", I("across() without `.cols`"), I("`everything()` to select all columns")) .cols

Do you want it to be `na.rm` or `na_rm`? `first()` and friends have `order_by` as an argument already so we'd end up with a mix of snake and dot case....

Randomly stumbled across a case where someone could use this https://stackoverflow.com/questions/73282239/retrieve-first-non-na-value-based-on-another-time-variable

It looks like you can use the `time_hour` column to resolve the ambiguity. It does look like the problem is that the `year->hour` columns don't contain information about whether or...