token and SliceStream do not play together well about combine HOT 2 CLOSED

The reason for the Clone bound is that combine assumes that Stream is a type that can be cloned (which is necessary for the or parser which implements alternation). Since Stream can be cloned it follows that its tokens must be cloneable as well (any token that does not implement Clone could still be duplicated by cloning the stream stream.uncons().clone() vs stream.clone().uncons() so there is no reason that they would not be possible to clone). If we then also assume that streams and tokens are cheap to clone (if they were expensive to clone then parsing would be slow) then it follows that the predicates might as well take Item instead of &Item as it is much more convenient in common cases such as Item = u8 or Item = char.

That was my reasoning in any case :).

As for the lifetime problem, that is not something I had considered actually. I can't think of anyway to make token available for that case as the token requires exactly the Item type since that is used to construct the error message if the parser fails

from combine.

Reasoning for Copy #44

from combine.