Export vec_locate_sorted_groups()

[DavisVaughan]

Looking at the prefix document, we've been thinking about using "locate" as the verb that generally deals with returning integer locations.

i.e. in theory all of these return an integer vector of locations

vec_locate_unique()
vec_locate_missing()
vec_locate_named()

While vec_locate_sorted_groups() doesn't return an integer vector, it is highly related to the idea of those other functions because the $loc column contains the locations of each unique key.

In the same line of thinking, I would rename vec_group_loc() to vec_locate_groups().

I can't think of any prefix that better differentiates between returning an integer vector of locations (like vec_locate_unique()) VS returning a df that contains a list column of integer locations (like vec_locate_groups()). I think since the ideas are so closely related, we can look past their difference in return value types in favor of having this nice "locate" prefix.

[lionel-]

I can't think of any prefix that better differentiates between returning an integer vector of locations (like vec_locate_unique()) VS returning a df that contains a list column of integer locations (like vec_locate_groups()). I think since the ideas are so closely related, we can look past their difference in return value types in favor of having this nice "locate" prefix.

I can't think of anything better either. You're probably right that trying to differentiate rich results and direct results would only produce a complicated naming scheme.