Shouldn't setequal ignore duplicates?

[juangomezduaso]

I thought that being in the group of set operations, setequal() would deem things like, say, mtcars and bind_rows(mtcars, mtcars) as equal, but it doesn´t.
i suppose this is the intended behavior, but in that case: Souldn´t this be explained somewhere in the documentation? My apologies if it already is, as I was unable to find it.
Taking into account that Rbase behavior in vectors ignores duplicates (and so bind_rows(mtcars,mtcars)[[1]] and mtcars[[1]] are equal) I think this clarification would be useful.

[DavisVaughan]

Minimal reprex showing the difference with base R

setequal(1, c(1, 1))
#> [1] TRUE

dplyr::setequal(data.frame(x = 1), data.frame(x = c(1, 1)))
#> [1] FALSE

Seems reasonable that we should be consistent and drop duplicates before checking