`StripStr` doesn't appear to maintain state across calls to `strip_next`.

[SamuelMcGowan]

When I pass "\x1b[" to anstream's StripStr::strip_next (and consume the iterator) , then call it again with "38;", the "38;" is not stripped as I would expect but is returned from the iterator. Printing out the StripStr shows that it is in the Ground state after the first call.

When I use StripBytes instead, the "38;" is stripped as I expected.

[epage]

I find it strange that the two have different behavior as they are so similar.

I don't think handling of partial ansi escape codes was part of the intent of the design but to handle batches of text.