C arrays decay, pointer arithmetic hides bounds, and slices are usually a convention. Musi examples keep the collection value and indexed access visible instead of relying on caller discipline.
int prices[] = {450, 120, 80};
int first_price = prices[0];let prices := [450, 120, 80];
let firstPrice := prices.[0];
firstPrice;Reading Arrays, Pointers, and Slices from C99
On the Musi side, Musi collection examples keep indexing, field access, and pipelines explicit so a reader can see where each value comes from. Read the shared example through C99 eyes: keep the useful instinct, then let Musi name shape, behavior, absence, and outside work in separate places.
False friend
Do not import lazy iterators, stream chains, table conventions, or pointer arithmetic unless the Musi example needs that behavior. For a C reader, the trap is treating convention as a contract; Musi class is not a C struct with function pointers; records/data carry shape, classes name behavior a type can provide.
When this pays off
Use this shape for prices, stops, animals, files, and other small batches where each step has a name. The C99 instinct still helps here: Keep the C habit of asking where memory, symbols, and failures come from.