Davis Vaughan

Oh I think I might have a potential explanation for this! With the `optional()` in place, there are two possible interpretations of `foo::bar`: ``` [foo::][bar] == [double_colon][identifier] [foo::bar] == [double_colon]...

Is it one or two functions in particular?

We did this with the `join_by()` DSL a little bit here with aliases: https://github.com/tidyverse/dplyr/blob/73742713bc61d4ef079e72b806143b23cb7c4871/R/join-by.R#L137 So that you can do `?closest` to get to the right place

I've added https://github.com/tidyverse/dplyr/commit/8ee46e6723b58ee8fb4538e2f6195bcd811f0fc1 to revert part of the `auto_copy()` error message changes so that we avoid a multidplyr failure. Probably good to still merge this though for future robustness

This has been fixed upstream in base R https://github.com/wch/r-source/commit/ae3f49fd3181b0c6b3b9b4bf646ab378c1a3316f For TDD, here is what I think we need to do to finish up the dplyr side. The changes take place...

Similarly, should `.editorconfig` drop `end_of_line = lf` (as done in the PR that fixed that python issue)?

Closed by https://github.com/tree-sitter/tree-sitter/pull/3284

Note that if you _don't_ have a Git tag that you can refer to, you can find the commit SHA that matches the commit that you sent to CRAN and...

> You probably want to increment the patch component in your default (dev) branch at this point, to reflect the insertion of this unplanned patch release. Concretely, it sounds like...

It may be that `str_separate_by_longer()` doesn't have the inconsistent length arguments, but `separate_by_longer()` does. With `str_separate_by_wider()` and `separate_by_wider()`, both take 1 vector/column and expand it into a data frame of...