Nicolas
Nicolas
I managed to implement `uncons_range` as a standalone method, but I can't implement `RangeStreamOnce` for now because of a lifetime mess with trait implementations and references lifetimes. It need the...
You're right about streaming RangeStream, it's not a good idea ! I changed my mind, I will not implement RangeStream. But for a simple streaming combine stream, it works perfectly...
I think the `tuple` function is still useful in case the tuple in question is not composed in another parser. Indeed, tuples implement `Parser`, not `FnMut`, so it is impossible...
The `Tuple` trait is still used to implement the `tuple` function. We can still do : ```rust let (i, result) = tuple((parser1, parser2))(i)?; ```
By doing this you allow any parser to be given as argument to `tuple`, and so you allow this code to compile : ```rust let (i, result) = tuple(tag("hello"))(i)?; ```...
I was considering the first solution too, I think it's a good idea! I will do that.
Done. It's a real breaking change, since it removes a function and change the signature of some others.
You are right, I forgot them ! It's fixed