Deprecate `all_equal()`

[hadley]

It's been questioning for awhile, and there doesn't seem to be much usage (https://cs.github.com/?scopeName=All+repos&scope=&q=all_equal+language%3AR)

[eitsupi]

Hi, I find this function dplyr::all_equal useful to compare the results of different dplyr backend calculations, etc.
If this is to be deprecated, what would be the recommended alternative?
Thanks.

[hadley]

@eitsupi all.equal()

[eitsupi]

Thanks for the reply.
I think it is useful that all_equal ignores the order of rows and columns of two data frames, because sometimes it is not expected that the order of rows and columns will always be the same.
For example, when porting a regular dplyr calculation to dbplyr+duckdb.
(I don't think all.equal or waldo::compare allows for different row order.)

[hadley]

@eitsupi in that case you should manually reorder them to match.