From af761914c9a94a9d54c1bcc2d4fff96a58674078 Mon Sep 17 00:00:00 2001 From: Hans Bolinder Date: Thu, 9 Jun 2016 13:18:07 +0200 Subject: Remove support for '...' in Maps types It is possible that '...' is added later (OTP 20.0), but for now we are not sure of all details. --- system/doc/reference_manual/typespec.xml | 18 ++++++------------ 1 file changed, 6 insertions(+), 12 deletions(-) (limited to 'system/doc/reference_manual/typespec.xml') diff --git a/system/doc/reference_manual/typespec.xml b/system/doc/reference_manual/typespec.xml index 9e26e9058d..f17e5df277 100644 --- a/system/doc/reference_manual/typespec.xml +++ b/system/doc/reference_manual/typespec.xml @@ -142,7 +142,7 @@ PairList :: Pair | Pair, PairList - Pair :: Type := Type %% notes a pair that must be present + Pair :: Type := Type %% denotes a pair that must be present | Type => Type TList :: Type @@ -174,19 +174,13 @@

The general form of maps is #{PairList}. The key types in - PairList are allowed to overlap, and if they do, the leftmost pair - takes precedence. A map value does not belong to this type if contains a key - that is not in PairList. + PairList are allowed to overlap, and if they do, the + leftmost pair takes precedence. A map pair has a key in + PairList if it belongs to this type.

- Because it is common to end a map type with any() => any() to denote - that keys that do not belong to any other pair in PairList are - allowed, and may map to any value, the shorthand notation ... is - allowed as the last pair of a map type. -

-

- Notice that the syntactic representation of map() is #{...} - (or #{_ => _}, or #{any() => any()}), not #{}. + Notice that the syntactic representation of map() is + #{any() => any()} (or #{_ => _}), not #{}. The notation #{} specifies the singleton type for the empty map.

-- cgit v1.2.3