consider accepting input like "dplyr::filter"?

[ijlyttle]

One of my favorite things to do is:

library("conflicted")
conflict_prefer("dplyr", "filter")

which does not provide the result I intend.
I think this happens because, in my head, I think "dplyr::filter".

Would you consider allowing the name argument to accept something like "dplyr::filter", or even dplyr::filter?

Happy to make a first stab at a PR, if you like.

Thanks!

[hadley]

Hmmm, I think it'd be rather hard to overhaul conflict_prefer() to accept this sort of syntax, so I think maybe a new name might be better?

And maybe we could avoid the problem in #75 by accepting multiple functions?

[hadley]

Name ideas:

• conflict_pick()
• conflict_favor() (my favo(u)rite expect for the UK/US issue)

[ijlyttle]

Repeating the comment in #82, I had been noodling on names and thought conflict_favor() could work for this case; the "f" could signify fully-qualified function names.

[ijlyttle]

I had thought also of conflict_pick() but there's a new pick() in tidy-eval (as you well know), which might be a bit too close.