mirror of
https://github.com/unisonweb/unison.git
synced 2024-09-17 13:27:30 +03:00
0031542faf
This is for consistency with the `cmark` style. Now the blocks we still pretty-print ourselves will match the bulk of them that `cmark` produces.
4.9 KiB
4.9 KiB
Regression test for updates which conflict with an existing ability constructor
https://github.com/unisonweb/unison/issues/2786
First we add an ability to the codebase.
Note that this will create the name Channels.send
as an ability constructor.
unique ability Channels where
send : a -> {Channels} ()
Loading changes detected in scratch.u.
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`:
ability Channels
scratch/main> add
⍟ I've added these definitions:
ability Channels
Now we update the ability, changing the name of the constructor, but, we simultaneously add a new top-level term with the same name as the constructor which is being removed from Channels.
unique ability Channels where
sends : [a] -> {Channels} ()
Channels.send : a -> ()
Channels.send a = ()
thing : '{Channels} ()
thing _ = send 1
Loading changes detected in scratch.u.
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`:
Channels.send : a -> ()
thing : '{Channels} ()
⍟ These names already exist. You can `update` them to your
new definition:
ability Channels
These should fail with a term/ctor conflict since we exclude the ability from the update.
scratch/main> update.old patch Channels.send
x These definitions failed:
Reason
term/ctor collision Channels.send : a -> ()
Tip: Use `help filestatus` to learn more.
scratch/main> update.old patch thing
⍟ I've added these definitions:
Channels.send : a -> ()
thing : '{Channels} ()
⍟ I've updated these names to your new definition:
ability Channels
If however, Channels.send
and thing
depend on Channels
, updating them should succeed since it pulls in the ability as a dependency.
unique ability Channels where
sends : [a] -> {Channels} ()
Channels.send : a -> ()
Channels.send a = sends [a]
thing : '{Channels} ()
thing _ = send 1
Loading changes detected in scratch.u.
I found and typechecked these definitions in scratch.u. If you
do an `add` or `update`, here's how your codebase would
change:
⊡ Previously added definitions will be ignored: Channels
⍟ These names already exist. You can `update` them to your
new definition:
Channels.send : a ->{Channels} ()
thing : '{Channels} ()
These updates should succeed since Channels
is a dependency.
scratch/main> update.old.preview patch Channels.send
I found and typechecked these definitions in scratch.u. If you
do an `add` or `update`, here's how your codebase would
change:
⊡ Previously added definitions will be ignored: Channels
⍟ These names already exist. You can `update` them to your
new definition:
Channels.send : a ->{Channels} ()
scratch/main> update.old.preview patch thing
I found and typechecked these definitions in scratch.u. If you
do an `add` or `update`, here's how your codebase would
change:
⊡ Previously added definitions will be ignored: Channels
⍟ These names already exist. You can `update` them to your
new definition:
Channels.send : a ->{Channels} ()
thing : '{Channels} ()
We should also be able to successfully update the whole thing.
scratch/main> update.old
⊡ Ignored previously added definitions: Channels
⍟ I've updated these names to your new definition:
Channels.send : a ->{Channels} ()
thing : '{Channels} ()
Constructor-term conflict
X.x = 1
Loading changes detected in scratch.u.
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`:
X.x : Nat
scratch/main2> add
⍟ I've added these definitions:
X.x : Nat
structural ability X where
x : ()
Loading changes detected in scratch.u.
I found and typechecked these definitions in scratch.u. If you
do an `add` or `update`, here's how your codebase would
change:
x These definitions would fail on `add` or `update`:
Reason
blocked structural ability X
ctor/term collision X.x
Tip: Use `help filestatus` to learn more.
This should fail with a ctor/term conflict.
scratch/main2> add
x These definitions failed:
Reason
blocked structural ability X
ctor/term collision X.x
Tip: Use `help filestatus` to learn more.