Playground here.
You can create an iterator with interleave_shortest that is longer than usize::MAX. However, since an iterator is lazy, you can use it (I assume you could take usize::MAX items from it at least). When you try to call size_hint on a long iterator created this way however, it panics, even though you can use the iterator itself.
I assume this is a bug in the size_hint method since I don't expect size_hint itself to panic -- it should just give me info. In this case, I would prefer (0, None) instead of panicking.
Playground here.
You can create an iterator with
interleave_shortestthat is longer thanusize::MAX. However, since an iterator is lazy, you can use it (I assume you could takeusize::MAXitems from it at least). When you try to callsize_hinton a long iterator created this way however, it panics, even though you can use the iterator itself.I assume this is a bug in the
size_hintmethod since I don't expectsize_hintitself to panic -- it should just give me info. In this case, I would prefer(0, None)instead of panicking.