Closed awwx closed 1 year ago
Thanks for the report, I can reproduce the bug too, even without the unusually-placed prime symbols.
Incidentally, I just stumbled on this bug while trying almost exactly the same thing as above, namely an "add item" predicate for a top-level var sig
. It doesn't seem to behave sensibly, so is this kind of thing even supported?
Incidentally, I just stumbled on this bug while trying almost exactly the same thing as above, namely an "add item" predicate for a top-level
var sig
. It doesn't seem to behave sensibly, so is this kind of thing even supported?
Not enough information to answer... Here @awwx ' issue is not related to item_added
, witness:
var sig Item {}
fact {
no Item
}
pred add_item_enabled {
#Item < 3
}
pred some_item_added {
one Item' - Item
}
fun added_item : Item {
Item' - Item
}
fact {
(eventually always add_item_enabled) implies (always eventually some_item_added)
}
Pinging @nmacedo
A simpler example where the problem still occurs:
var sig Item {}
fact {
no Item and some Item'
}
fun added_item : Item {
Item'
}
Fixed for 6.2.
Alloy 6.1.0, SAT4J openjdk version "11.0.13" 2021-10-19 Ubuntu 21.04
This example might not make much sense as a model since I was just playing around while learning Alloy and then I cut it down to a minimal test case, but since it causes a crash I thought I'd pass it along for you...