You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I can't tell if this is a bug or me not understanding what vec_locate_matches() does.
In this example, I would expect that nrow(matches) == length(needles), because of the filter = "max" arg. But the last two needles entries have multiple corresponding haystack matches. Is this expected?
I just realized it's because the matched entries are duplicates in haystack. Calling unique(haystack) or passing arg multiple = "any" leads to the expected output from vec_locate_matches().
I can't tell if this is a bug or me not understanding what
vec_locate_matches()
does.In this example, I would expect that
nrow(matches) == length(needles)
, because of thefilter = "max"
arg. But the last twoneedles
entries have multiple correspondinghaystack
matches. Is this expected?Created on 2025-01-17 with reprex v2.1.1
The text was updated successfully, but these errors were encountered: