API

Current API is not bad, but it has some problems. Because this crate implements standard `Iterator` trait simd iterators can be used in for loops(and they are currently used for example in benchmarks), but inside those loops there is no uneven collection handling, this I think can be added, but it would reduce performance. Second thing is that inside for loops there is no in place mutation, you need to manually store. I think it would be better to just have internal iterator trait, and implement functionality on top of it, it would also allow dropping simd prefix on iterators methods. It would make the API more similar to the standard library, with exception of providing defaults. Thoughts?

Start by reading the crate's current standard Iterator implementations and the benchmarks, which the issue identifies as existing users of the iterators. Compare the proposed internal iterator trait, uneven collection handling, in-place mutation, and method naming with the current API. Done would require an agreed API design before implementation begins.

Escrito por el modelo de indexación a partir del texto del issue.