Collections and Literals

Examples on this page that name collection interfaces or concrete collection classes assume import klyn.collections at module level. Literal syntax itself remains available without writing the class names explicitly.

import klyn.collections

Prefixes are short on purpose. They encode the storage contract directly in the syntax: f means fixed-size, i means immutable, s means synchronized/thread-safe, and l means linked-list semantics. Compound prefixes combine contracts: fs is fixed-size synchronized, and ls is linked-list synchronized.

data = f:[10, 20, 30]      # Array<Int>           fixed-size contiguous array

data = fs:[10, 20, 30]     # ArraySync<Int>       fixed-size thread-safe array

data = i:[10, 20, 30]      # ImmutableList<Int>   homogeneous immutable sequence

data = [10, 20, 30]       # ArrayList<Int>       dynamic-size list

data = s:[10, 20, 30]      # ArrayListSync<Int>   dynamic-size thread-safe list

data = l:[10, 20, 30]      # LinkedList<Int>      dynamic-size linked-list contract

data = ls:[10, 20, 30]     # LinkedListSync<Int>  thread-safe linked-list contract

data = {10, 20, 30}       # HashSet<Int>         unique unordered values

data = s:{10, 20, 30}      # HashSetSync<Int>     thread-safe unique unordered values

mapping = {"a": 1, "b": 2} # HashMap<String, Int>

Empty literals need context. Use an explicit annotation or constructor when the element type cannot be inferred from values.

names as ArrayList<String> = []
ids as HashSet<UInt> = HashSet<UInt>()
index as HashMap<String, Int> = {}

Array<T> is a fixed-size contiguous array. Its size is decided at construction time and never changes. Use it when the number of slots is known and indexed access is the dominant operation.

values = f:[30, 10, 20]
values.sort()
assert values[0] == 10
assert values.size == 3

The explicit allocation form T[n] creates a fixed array with n neutral-valued slots. Use T[] in type annotations when an API accepts an array whose size is determined at runtime.

buffer as Byte[] = Byte[4096]
names as String[] = String[3]

assert buffer.size == 4096uL
assert names.size == 3uL

ArraySync<T> has the same fixed-size contract, but runtime operations are synchronized for shared mutable access.

shared = fs:[1, 2, 3]
shared[0] = 10
assert shared is ArraySync<Int>

ArrayList<T> is the default list literal. It grows dynamically and supports indexed reads, indexed writes, appends, sorting, reversing, and membership checks.

data = [10, 20, 30]
assert data is ArrayList<Int>
assert data[0] == 10
assert data[-1] == 30

data[1] = 2000
data.add(40)

ArrayListSync<T> exposes the same typed list API with synchronized storage. Prefer the non-synchronized version for single-threaded hot paths.

shared = s:[10, 20, 30]
shared.add(40)
assert shared is ArrayListSync<Int>

l:[...] creates a LinkedList<T>, and ls:[...] creates the synchronized LinkedListSync<T>. They expose the same List<T> contract as dynamic arrays. In the current runtime, linked lists use optimized native list storage, so the literal is primarily a semantic/API choice. Prefer the type that communicates the API contract instead of treating the prefix as a low-level storage escape hatch.

linked = l:[10, 20, 30]
linked.removeAt(1)
assert linked is LinkedList<Int>
assert linked[1] == 30
assert linked.toString() == "l:[10, 30]"

sharedLinked = ls:[10, 20, 30]
sharedLinked.add(40)
assert sharedLinked is LinkedListSync<Int>

Copying from another collection now goes through constructors, not static factories.

immutable as IList<Int> = i:[1, 2, 3]
mutable = ArrayList<Int>(immutable)
syncMutable = ArrayListSync<Int>(mutable)
linked = LinkedList<Int>(immutable)
syncLinked = LinkedListSync<Int>(linked)

Mutable lists provide indexed insertion, bulk insertion, indexed removal, and forward or reverse searches. Search methods return -1 when no element matches.

values = [10, 20, 10]

assert values.indexOf(10) == 0
assert values.indexOf(10, 1) == 2
assert values.lastIndexOf(10) == 2

values.add(1, 15)
values.addAll([30, 40])
values.addAll(2, (16, 17))
values.removeAt(0)

addAll is deliberately separate from add: a list can contain another list as one element. += is the concise bulk-append form and accepts an IList<T>, a Set<T>, or a tuple. The + operator concatenates two values of the same concrete list family into a new list.

left = [10, 20]
right = [30, 40]
combined = left + right

left += i:[30, 40]
left += (50, 60)

assert combined == [10, 20, 30, 40]
assert left == [10, 20, 30, 40, 50, 60]

i:[...] creates an ImmutableList<T>: a homogeneous immutable sequence exposed through IList<T>. It is the right choice when callers should read values without mutating the collection.

values as IList<Int> = i:[10, 20, 30]
assert values[1] == 20
assert values.size == 3

Parenthesized comma expressions build positional tuples. Tuples are fixed positional values and may be heterogeneous. They are not List<T>.

single = (1)
pair = ("age", 42)
singletonTuple = (1,)

assert single is Int
assert singletonTuple is Tuple<Int>

A trailing comma is what makes a one-element tuple. Use i:[...] for a homogeneous immutable sequence.

HashSet<T> stores unique values with average O(1) add, lookup, and remove. Duplicate literal entries are ignored by the set contract.

colors = {"red", "blue", "red"}
assert colors is HashSet<String>
assert colors.size == 2
assert "red" in colors

Use s:{...} for the synchronized set variant.

sharedColors = s:{"red", "blue"}
assert sharedColors is HashSetSync<String>

An empty brace literal {} is a map, not a set. Empty sets must therefore be constructed explicitly.

empty = HashSet<String>()
copy = HashSet<String>(["red", "blue"])

Map literals use key: value pairs and infer both key and value types. The default concrete literal type is HashMap<K, V>.

config = {
    "fullscreen": true,
    "theme": "dark"
}

config["theme"] = "light"
assert config is HashMap<String, Object>

Use constructors to copy maps or build a map from parallel key/value lists.

keys = ["a", "b", "c"]
values = [1, 2, 3]
index = HashMap<String, Int>(keys, values)
copy = HashMap<String, Int>(index)
shared = HashMapSync<String, Int>(copy)

Index access raises KeyException when a key is absent. Use the generic get<R>(key, defaultValue) form when a typed fallback is appropriate. The result type R is inferred from the default value, which is particularly useful for heterogeneous Object maps.

config as MapCollection<String, Object> = {
    "fullscreen": true,
    "theme": "dark",
    "retryCount": 3
}

fullscreen as Boolean = config.get("fullscreen", false)
theme as String = config.get("theme", "light")
timeout as Int = config.get("missingTimeout", 30)
explicit as String = config.get<String>("theme", "light")

assert fullscreen
assert theme == "dark"
assert timeout == 30

ints = [10, 20, 30]                  # ArrayList<Int>
doubles = [10, 20, 30.0]             # ArrayList<Double>
fixed = f:[10, 20, 30]                # Array<Int>
syncFixed = fs:[10, 20, 30]           # ArraySync<Int>
immutable = i:[10, 20, 30]            # ImmutableList<Int>
shared = s:[10, 20, 30]               # ArrayListSync<Int>
linked = l:[10, 20, 30]               # LinkedList<Int>
syncLinked = ls:[10, 20, 30]          # LinkedListSync<Int>
setValues = {10, 20, 30}             # HashSet<Int>
mixed = [10, true, "hello"]          # ArrayList<Object>
mapping = {"a": 1, "b": 2}          # HashMap<String, Int>

a, b, c = [10, 100, 1000]
x, y, z = (1, 2, 3)

Unpacking works with list-like values and tuples when the number of values matches the number of targets.

Fixed arrays and dynamic array lists support [start:stop:step]. Omitted bounds and negative indexes follow the same rules as string slices, and the stop index is exclusive. A zero step is invalid.

data = [10, 20, 30, 40, 50]

assert data[1:4] == [20, 30, 40]
assert data[:3] == [10, 20, 30]
assert data[::2] == [10, 30, 50]
assert data[::-1] == [50, 40, 30, 20, 10]

Slice assignment replaces the selected range. Dynamic lists accept compatible list, fixed array, immutable-list, synchronized-list, or tuple values. Fixed arrays keep their fixed-size contract, so the replacement must fit the selected slots.

data[1:4] = s:[200, 300, 400]
assert data == [10, 200, 300, 400, 50]

fixed = f:[10, 20, 30, 40]
fixed[1:3] = [200, 300]
assert fixed == f:[10, 200, 300, 40]

Comprehensions build a new collection by iterating over an existing collection and evaluating an expression for each element. The result is still statically typed: the compiler infers the output element type from the generated expression, not from a dynamic runtime scan.

source = [10, 20, 30]

doubled = [x * 2 for x in source]       # ArrayList<Int>
assert doubled == [20, 40, 60]

The iteration variable belongs to the comprehension only. It does not leak into the enclosing scope after construction, which prevents accidental reuse of the last iterated value.

Add an if clause when only some elements should be kept. The filter is evaluated before appending the transformed value to the result collection.

large = [x * 2 for x in source if x > 15]
assert large == [40, 60]

The prefix before the comprehension controls the concrete result type, exactly like it does for plain literals.

dynamic = [x + 1 for x in source]       # ArrayList<Int>
shared = s:[x + 1 for x in source]       # ArrayListSync<Int>
linked = l:[x + 1 for x in source]       # LinkedList<Int>
syncLinked = ls:[x + 1 for x in source]  # LinkedListSync<Int>
immutable = i:[x + 1 for x in source]    # ImmutableList<Int>
fixed = f:[x + 1 for x in source]        # Array<Int>
syncFixed = fs:[x + 1 for x in source]   # ArraySync<Int>

Use fixed-array comprehensions when the result is read mostly by index and should not grow after construction. Use linked-list comprehensions when an API should explicitly expose LinkedList<T> or LinkedListSync<T>. Use synchronized comprehensions only when the resulting collection is shared across threads; the unsynchronized variants remain the better default for hot paths.

names = ["Ada", "Grace", "Linus"]
upperNames = f:[name.upper() for name in names]
assert upperNames is Array<String>
assert upperNames[0] == "ADA"

Comprehensions can also change the element type. In the next example, the source is a list of strings while the result is a list of integers.

words = ["Klyn", "is", "fast"]
sizes = [word.size for word in words]   # ArrayList<ULong>
assert sizes[0] == 4u

Map comprehensions use keyExpr: valueExpr. When the source is a map, iteration may bind both the key and the value with for key, value in map.

scores = {"alice": 12, "bob": 7, "chloe": 18}

bonus = {name.upper(): score + 1 for name, score in scores}
assert bonus["ALICE"] == 13

passing = {name: score for name, score in scores if score >= 10}
assert "bob" not in passing

There is no special set-comprehension syntax. Build the intermediate list with a comprehension, then pass it to a set constructor when uniqueness is the target contract.

raw = [1, 2, 2, 3, 3, 3]
uniqueDoubled = HashSet<Int>([x * 2 for x in raw])
assert uniqueDoubled.size == 3

values = [10, 20, 30]
for value in values:
    print(value)

for key in config.keys():
    print(key)

for value in config.values():
    print(value)

for entry in config.items():
    print(entry)

Direct map iteration yields keys. Use helper views when you want values or key/value tuples.