Best way to call `vec.contains` in this case

[samuelpilz]

I have: data: Vec<String> (unsorted) and some s: &str. I want to know if data contains s. To my surprise, data.contains(s) does not work because s is not &String. Note that BTreeMap::contains_key allows this.

Is data.iter().any(...) really my best option?

[H2CO3]

I believe it is.

[vague]

Sort of surprising, but rational in essence:

// impl<T> [T]
pub fn contains(&self, x: &T) -> bool
where
    T: PartialEq<T>,

// impl<K, V, A> BTreeMap<K, V, A> where A: Allocator + Clone
pub fn contains_key<Q>(&self, key: &Q) -> bool
where
    K: Borrow<Q> + Ord,
    Q: Ord + ?Sized, 

For Vec<String>, (&[String]).contains(&String) is the only form allowed by definition.
For BTreeMap<String, V, A>, btreemap.contains_key(&str) is acceptable because of String: Borrow<str> + Ord and str: Ord + ?Sized.

[samuelpilz]

Sure, I understand the signatures. But it is surprising to me that they are the way they are. Probably for historic reasons? maybe because (earlier) type inference handles the non-Borrow one better?

[quinedot]

It was attempted but broke inference too much. See #42671 and the links within.