2022-01-05 03:58:15 +03:00
|
|
|
The order of a set of abilities is normalized before hashing.
|
|
|
|
|
2024-07-10 17:46:18 +03:00
|
|
|
``` unison
|
2022-01-05 03:58:15 +03:00
|
|
|
unique ability Foo where
|
|
|
|
foo : ()
|
|
|
|
|
|
|
|
unique ability Bar where
|
|
|
|
bar : ()
|
|
|
|
|
|
|
|
term1 : () ->{Foo, Bar} ()
|
|
|
|
term1 _ = ()
|
|
|
|
|
|
|
|
term2 : () ->{Bar, Foo} ()
|
|
|
|
term2 _ = ()
|
|
|
|
```
|
|
|
|
|
2024-07-10 19:17:15 +03:00
|
|
|
``` ucm
|
2022-01-05 03:58:15 +03:00
|
|
|
|
2023-12-22 14:55:24 +03:00
|
|
|
Loading changes detected in scratch.u.
|
|
|
|
|
2022-01-05 03:58:15 +03:00
|
|
|
I found and typechecked these definitions in scratch.u. If you
|
|
|
|
do an `add` or `update`, here's how your codebase would
|
|
|
|
change:
|
|
|
|
|
|
|
|
⍟ These new definitions are ok to `add`:
|
|
|
|
|
2024-01-04 11:42:12 +03:00
|
|
|
ability Bar
|
|
|
|
ability Foo
|
2022-02-08 05:29:57 +03:00
|
|
|
term1 : '{Bar, Foo} ()
|
|
|
|
term2 : '{Bar, Foo} ()
|
2022-01-05 03:58:15 +03:00
|
|
|
|
|
|
|
```
|
2024-07-10 19:17:15 +03:00
|
|
|
``` ucm
|
2024-06-12 01:22:09 +03:00
|
|
|
scratch/main> add
|
2022-01-05 03:58:15 +03:00
|
|
|
|
|
|
|
⍟ I've added these definitions:
|
|
|
|
|
2024-01-04 11:42:12 +03:00
|
|
|
ability Bar
|
|
|
|
ability Foo
|
2022-02-08 05:29:57 +03:00
|
|
|
term1 : '{Bar, Foo} ()
|
|
|
|
term2 : '{Bar, Foo} ()
|
2022-01-05 03:58:15 +03:00
|
|
|
|
2024-06-12 01:22:09 +03:00
|
|
|
scratch/main> names term1
|
2022-01-05 03:58:15 +03:00
|
|
|
|
|
|
|
Term
|
2022-02-08 05:29:57 +03:00
|
|
|
Hash: #8hum58rlih
|
2022-01-05 03:58:15 +03:00
|
|
|
Names: term1 term2
|
|
|
|
|
|
|
|
```
|