Stargateur

```rust pub fn fold_until0( parser: P, until: Until, init: Init, fold: Fold, ) -> impl FnMut(Input) -> IResult where Input: InputTake + InputIter + InputLength + Clone, F: Parser, Until:...

My personal way to import nom module is as follow: ```rust use nom::{ branch, bytes::complete as bytes, character::complete as character, combinator, multi, sequence, AsChar, IResult as Outcome, }; pub(crate) fn...

I could see a world where we inverse `foo::complete` and `foo::streaming` for `complete::foo` and `streaming::foo` this make sense cause: - I don't think there is a case where in the...

> Could you tell me where Im forcing complete input? If one of the operand or operator parser returns Needed it should just bubble to the caller. As far as...

This would catch every failure of any underline parser, it's probably a bad idea. I think you are trying to opposite to combinator concept with your `cut` usage. Why not:...

> that would immediately and incorrectly parse the 0 in 0xFF as a decimal 0 and then stop there, wouldn't it? Yes, if `dec_uint` match one `0`, was just a...

Let's forget about your use case I think we mixed thing. That an interesting way to use Failure indeed. I have not yet see this pattern wanted to be used...

Thank it's a very good argument, again you clearly make your point about uncut use case. But my point is that Failure is also used as runtime error of a...

> > > For anybody that comes in the future, this was how I resolved this case for me: > > ```rust > let mut terms = Vec::new(); > >...

you can't do that, offset need to be used with the same origin, aka pointer, and the argument must be "same or after" `self`. I think we should update doc...