diff options
| author | Kostis Sagonas <[email protected]> | 2019-06-19 10:08:02 +0200 |
|---|---|---|
| committer | Hans Bolinder <[email protected]> | 2019-06-24 14:01:17 +0200 |
| commit | d0a08a7b8a8d4dd8d825f5bc0d2ee9687c549516 (patch) | |
| tree | 787fbcdaa022bdcde881086262c1f5982a8c3869 /bootstrap/lib/stdlib/ebin/gen_statem.beam | |
| parent | 8f67452510ce9544331d5d3a82cd152d2333bc0e (diff) | |
| download | otp-d0a08a7b8a8d4dd8d825f5bc0d2ee9687c549516.tar.gz otp-d0a08a7b8a8d4dd8d825f5bc0d2ee9687c549516.tar.bz2 otp-d0a08a7b8a8d4dd8d825f5bc0d2ee9687c549516.zip | |
The map() type is an alias; not a predefined type
This pull request corrects an historical accident.
At some point in time, the set of Erlang terms was extended to include
maps, and at that time the `map()' type was also introduced to the
language as an easy, albeit quite coarse, way to declare map terms.
At some later point in time, the type language was extended with the
ability to declare _type associations_ in maps and also with a notation
to declare mandatory (:=) and optional (=>) type associations.
At that point in time, it should have been realized that the `map()'
type is nothing more than an alias (for `#{any() => any()}') instead
of being a _predefined_ type. (The situation is analogous to e.g.
the `binary()' type being just an alias for `<<_:_*8>>'.)
This pull request corrects the documentation (the reference manual).
Diffstat (limited to 'bootstrap/lib/stdlib/ebin/gen_statem.beam')
0 files changed, 0 insertions, 0 deletions