From 44cd26f2cebd760a53aa4ff1b7779e718a101650 Mon Sep 17 00:00:00 2001 From: Bruce Hill Date: Sun, 6 Apr 2025 22:45:02 -0400 Subject: Rename Array -> List in all code and docs --- docs/nums.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs/nums.md') diff --git a/docs/nums.md b/docs/nums.md index 36dedcac..34e513ef 100644 --- a/docs/nums.md +++ b/docs/nums.md @@ -27,7 +27,7 @@ differentiate between possibly-NaN values and definitely-not-NaN values. Tomo has a separate concept for expressing the lack of a defined value: optional types. Consequently, Tomo has merged these two concepts, so `NaN` is called `none` and has the type `Num?` or `Num32?`. In this way, it's no -different from optional integers or optional arrays. This means that if a +different from optional integers or optional lists. This means that if a variable has type `Num`, it is guaranteed to not hold a NaN value. This also means that operations which may produce NaN values have a result type of `Num?`. For example, division can take two non-NaN values and return a result -- cgit v1.2.3