Collections and iteration
List, Map, Set, Stack and Queue as traits over a shared Iterate, plus slices, pipelines and collectors.
Diese Seite gibt es noch nicht auf Deutsch, deshalb steht sie hier auf Englisch. Zur englischen Seite
The collection types, one trait per kind; how for and a pipeline pull values out of anything Iterate; and how a
pipeline's terminal operation decides where they end up.
What belongs here#
Every collection trait and its default implementations, indexing and slicing, for, lazy pipeline stages and their
terminal operations, and collectors. What does not belong here: the two shared types that carry values between tasks
over time, Source and Sink, which are in
concurrency-and-streams/; the String type itself, which is in
values-and-types/ even though a String shares Slice with a List.
Pages#
- The collection traits - Every kind of collection is a trait - List, Set, Map, Stack, Queue - so a signature names what a value can do, and only its construction names the data structure behind it.
- Lists - List is the ordered, indexable sequence behind the literal [1, 2, 3], with ArrayList as the default implementation and a verb paired with a participle for every change.
- Maps and sets - The literal ["a": 1] builds a Map, a Set is built from a list literal instead of having one of its own, and both iterate in insertion order while comparing regardless of it.
- Stacks and queues - Stack is LIFO with push, pop and peek, Queue is FIFO with enqueue, dequeue and peek - the words everybody knows for each structure.
- Slices - list[from..to] answers a List that shares storage and starts at index 0 again; as a var path the same expression is a window into the original instead.
- Iterating - for pulls from Iterator.next() through Iterate.iterate(), and the subject of a for is evaluated once into a temporary, so changing it inside the loop does not affect what is walked.
- Changing elements in place - for var item in items binds each slot of a container in turn, so a change of item changes the container itself - over a List, an Array, a window, the values of a Map, and any type with MutableIndex.
- Pipelines - A pipeline is a source, zero or more lazy stages and exactly one terminal operation, and nothing runs until the terminal operation pulls a value through.
- Collectors - An Accumulator describes what to do with the values of a pipeline and is the state of one run at the same time, because a value is a copy; collect fills a copy of the one it is given.