cue: make integer literals integer only
Most of the spec was already updated.
This avoids a lot of unintuitive behavior where
stemming from the fact int did not subsume 1.
Dealing with floats is now more cumbersome,
but users can use the more convenient number.
It may be worth it renaming int to integer or to
rename number to num to be consistent. But
maybe the naming is okay as is.
Change-Id: Iaf58f131a2507e9b7c1856bdf65cef5aa10998ad
Reviewed-on: https://cue-review.googlesource.com/c/cue/+/1982
Reviewed-by: Jonathan Amsterdam <jba@google.com>
diff --git a/doc/ref/spec.md b/doc/ref/spec.md
index 2dbc8ac..5263f29 100644
--- a/doc/ref/spec.md
+++ b/doc/ref/spec.md
@@ -1934,6 +1934,7 @@
- Integer values are comparable and ordered, in the usual way.
- Floating-point values are comparable and ordered, as per the definitions
for binary coded decimals in the IEEE-754-2008 standard.
+- Floating point numbers may be compared with integers.
- String values are comparable and ordered, lexically byte-wise after
normalization to Unicode normal form NFC.
- Struct are not comparable.
@@ -1948,6 +1949,7 @@
```
3 < 4 // true
+3 < 4.0 // true
null == 2 // false
null != {} // true
{} == {} // _|_: structs are not comparable against structs
