Tweak
This commit is contained in:
parent
7861341951
commit
df94b7a8c6
|
@ -880,9 +880,9 @@ types.[^why-dictionaries]
|
||||||
predicate to programmers, and so if a data type demands a special
|
predicate to programmers, and so if a data type demands a special
|
||||||
equivalence predicate, as `Dictionary`, `Set` and `Float` all do,
|
equivalence predicate, as `Dictionary`, `Set` and `Float` all do,
|
||||||
then the type should be included in the base language. Otherwise,
|
then the type should be included in the base language. Otherwise,
|
||||||
it can be represented as a `Record` and treated separately. Both
|
it can be represented as a `Record` and treated separately.
|
||||||
`Boolean` and `String` are seeming exceptions: they merit
|
`Boolean`, `String` and `Symbol` are seeming exceptions: they
|
||||||
inclusion because of their cultural importance.
|
merit inclusion because of their cultural importance.
|
||||||
|
|
||||||
All of these conventions are optional. They form a layer atop the core
|
All of these conventions are optional. They form a layer atop the core
|
||||||
`Value` structure. Non-domain-specific tools do not in general need to
|
`Value` structure. Non-domain-specific tools do not in general need to
|
||||||
|
|
Loading…
Reference in New Issue