Module shipyard::iterators[][src]

Structs

Chunk iterator over a single component.
Returns slices size long except for the last one that might be smaller.

Chunk iterator over 2 components.
Returns a tuple of size long slices and not single elements.
The last chunk’s length will be smaller than size if size does not divide the iterator’s length perfectly.

Chunk iterator over 3 components.
Returns a tuple of size long slices and not single elements.
The last chunk’s length will be smaller than size if size does not divide the iterator’s length perfectly.

Chunk iterator over 4 components.
Returns a tuple of size long slices and not single elements.
The last chunk’s length will be smaller than size if size does not divide the iterator’s length perfectly.

Chunk iterator over 5 components.
Returns a tuple of size long slices and not single elements.
The last chunk’s length will be smaller than size if size does not divide the iterator’s length perfectly.

Chunk iterator over 6 components.
Returns a tuple of size long slices and not single elements.
The last chunk’s length will be smaller than size if size does not divide the iterator’s length perfectly.

Chunk iterator over 7 components.
Returns a tuple of size long slices and not single elements.
The last chunk’s length will be smaller than size if size does not divide the iterator’s length perfectly.

Chunk iterator over 8 components.
Returns a tuple of size long slices and not single elements.
The last chunk’s length will be smaller than size if size does not divide the iterator’s length perfectly.

Chunk iterator over 9 components.
Returns a tuple of size long slices and not single elements.
The last chunk’s length will be smaller than size if size does not divide the iterator’s length perfectly.

Chunk iterator over 10 components.
Returns a tuple of size long slices and not single elements.
The last chunk’s length will be smaller than size if size does not divide the iterator’s length perfectly.

Chunk iterator over a single component.
Returns slices size long, to get the remaining items (if any) use the remainder method.

Chunk iterator over 2 components.
Returns a tuple of size long slices and not single elements.
ChunkExact will always return a slice with the same length.
To get the remaining items (if any) use the remainder method.

Chunk iterator over 3 components.
Returns a tuple of size long slices and not single elements.
ChunkExact will always return a slice with the same length.
To get the remaining items (if any) use the remainder method.

Chunk iterator over 4 components.
Returns a tuple of size long slices and not single elements.
ChunkExact will always return a slice with the same length.
To get the remaining items (if any) use the remainder method.

Chunk iterator over 5 components.
Returns a tuple of size long slices and not single elements.
ChunkExact will always return a slice with the same length.
To get the remaining items (if any) use the remainder method.

Chunk iterator over 6 components.
Returns a tuple of size long slices and not single elements.
ChunkExact will always return a slice with the same length.
To get the remaining items (if any) use the remainder method.

Chunk iterator over 7 components.
Returns a tuple of size long slices and not single elements.
ChunkExact will always return a slice with the same length.
To get the remaining items (if any) use the remainder method.

Chunk iterator over 8 components.
Returns a tuple of size long slices and not single elements.
ChunkExact will always return a slice with the same length.
To get the remaining items (if any) use the remainder method.

Chunk iterator over 9 components.
Returns a tuple of size long slices and not single elements.
ChunkExact will always return a slice with the same length.
To get the remaining items (if any) use the remainder method.

Chunk iterator over 10 components.
Returns a tuple of size long slices and not single elements.
ChunkExact will always return a slice with the same length.
To get the remaining items (if any) use the remainder method.

Loose iterator over 2 components.

Loose iterator over 3 components.

Loose iterator over 4 components.

Loose iterator over 5 components.

Loose iterator over 6 components.

Loose iterator over 7 components.

Loose iterator over 8 components.

Loose iterator over 9 components.

Loose iterator over 10 components.

Non packed iterator over 2 components.

Non packed iterator over 3 components.

Non packed iterator over 4 components.

Non packed iterator over 5 components.

Non packed iterator over 6 components.

Non packed iterator over 7 components.

Non packed iterator over 8 components.

Non packed iterator over 9 components.

Non packed iterator over 10 components.

ParLoose2parallel

Loose parallel iterator over 2 components.

ParLoose3parallel

Loose parallel iterator over 3 components.

ParLoose4parallel

Loose parallel iterator over 4 components.

ParLoose5parallel

Loose parallel iterator over 5 components.

ParLoose6parallel

Loose parallel iterator over 6 components.

ParLoose7parallel

Loose parallel iterator over 7 components.

ParLoose8parallel

Loose parallel iterator over 8 components.

ParLoose9parallel

Loose parallel iterator over 9 components.

ParLoose10parallel

Loose parallel iterator over 10 components.

Non packed parallel iterator over 2 components.

Non packed parallel iterator over 3 components.

Non packed parallel iterator over 4 components.

Non packed parallel iterator over 5 components.

Non packed parallel iterator over 6 components.

Non packed parallel iterator over 7 components.

Non packed parallel iterator over 8 components.

Non packed parallel iterator over 9 components.

Non packed parallel iterator over 10 components.

ParTight1parallel

Tight parallel iterator over a single component.

ParTight2parallel

Tight parallel iterator over 2 components.
Tight iterators are fast but are limited to components tightly packed together.

ParTight3parallel

Tight parallel iterator over 3 components.
Tight iterators are fast but are limited to components tightly packed together.

ParTight4parallel

Tight parallel iterator over 4 components.
Tight iterators are fast but are limited to components tightly packed together.

ParTight5parallel

Tight parallel iterator over 5 components.
Tight iterators are fast but are limited to components tightly packed together.

ParTight6parallel

Tight parallel iterator over 6 components.
Tight iterators are fast but are limited to components tightly packed together.

ParTight7parallel

Tight parallel iterator over 7 components.
Tight iterators are fast but are limited to components tightly packed together.

ParTight8parallel

Tight parallel iterator over 8 components.
Tight iterators are fast but are limited to components tightly packed together.

ParTight9parallel

Tight parallel iterator over 9 components.
Tight iterators are fast but are limited to components tightly packed together.

ParTight10parallel

Tight parallel iterator over 10 components.
Tight iterators are fast but are limited to components tightly packed together.

ParUpdate1parallel

Update parallel iterator over a single component.

Tight iterator over a single component.

Tight iterator over 2 components.
Tight iterators are fast but are limited to components tightly packed together.

Tight iterator over 3 components.
Tight iterators are fast but are limited to components tightly packed together.

Tight iterator over 4 components.
Tight iterators are fast but are limited to components tightly packed together.

Tight iterator over 5 components.
Tight iterators are fast but are limited to components tightly packed together.

Tight iterator over 6 components.
Tight iterators are fast but are limited to components tightly packed together.

Tight iterator over 7 components.
Tight iterators are fast but are limited to components tightly packed together.

Tight iterator over 8 components.
Tight iterators are fast but are limited to components tightly packed together.

Tight iterator over 9 components.
Tight iterators are fast but are limited to components tightly packed together.

Tight iterator over 10 components.
Tight iterators are fast but are limited to components tightly packed together.

Update iterator over a single component.

Update iterator over 2 components.

Update iterator over 3 components.

Update iterator over 4 components.

Update iterator over 5 components.

Update iterator over 6 components.

Update iterator over 7 components.

Update iterator over 8 components.

Update iterator over 9 components.

Update iterator over 10 components.

Enums

Iterator over a single component.

Iterator over 2 components.
This enum allows to abstract away what kind of iterator you really get. That doesn’t mean the performance will suffer, the compiler will (almost) always optimize it away.

Iterator over 3 components.
This enum allows to abstract away what kind of iterator you really get. That doesn’t mean the performance will suffer, the compiler will (almost) always optimize it away.

Iterator over 4 components.
This enum allows to abstract away what kind of iterator you really get. That doesn’t mean the performance will suffer, the compiler will (almost) always optimize it away.

Iterator over 5 components.
This enum allows to abstract away what kind of iterator you really get. That doesn’t mean the performance will suffer, the compiler will (almost) always optimize it away.

Iterator over 6 components.
This enum allows to abstract away what kind of iterator you really get. That doesn’t mean the performance will suffer, the compiler will (almost) always optimize it away.

Iterator over 7 components.
This enum allows to abstract away what kind of iterator you really get. That doesn’t mean the performance will suffer, the compiler will (almost) always optimize it away.

Iterator over 8 components.
This enum allows to abstract away what kind of iterator you really get. That doesn’t mean the performance will suffer, the compiler will (almost) always optimize it away.

Iterator over 9 components.
This enum allows to abstract away what kind of iterator you really get. That doesn’t mean the performance will suffer, the compiler will (almost) always optimize it away.

Iterator over 10 components.
This enum allows to abstract away what kind of iterator you really get. That doesn’t mean the performance will suffer, the compiler will (almost) always optimize it away.

Parallel iterator over a single component.

Parallel iterator over 2 components.
This enum allows to abstract away what kind of iterator you really get. That doesn’t mean the performance will suffer, the compiler will (almost) always optimize it away.

Parallel iterator over 3 components.
This enum allows to abstract away what kind of iterator you really get. That doesn’t mean the performance will suffer, the compiler will (almost) always optimize it away.

Parallel iterator over 4 components.
This enum allows to abstract away what kind of iterator you really get. That doesn’t mean the performance will suffer, the compiler will (almost) always optimize it away.

Parallel iterator over 5 components.
This enum allows to abstract away what kind of iterator you really get. That doesn’t mean the performance will suffer, the compiler will (almost) always optimize it away.

Parallel iterator over 6 components.
This enum allows to abstract away what kind of iterator you really get. That doesn’t mean the performance will suffer, the compiler will (almost) always optimize it away.

Parallel iterator over 7 components.
This enum allows to abstract away what kind of iterator you really get. That doesn’t mean the performance will suffer, the compiler will (almost) always optimize it away.

Parallel iterator over 8 components.
This enum allows to abstract away what kind of iterator you really get. That doesn’t mean the performance will suffer, the compiler will (almost) always optimize it away.

Parallel iterator over 9 components.
This enum allows to abstract away what kind of iterator you really get. That doesn’t mean the performance will suffer, the compiler will (almost) always optimize it away.

Parallel iterator over 10 components.
This enum allows to abstract away what kind of iterator you really get. That doesn’t mean the performance will suffer, the compiler will (almost) always optimize it away.