-
Notifications
You must be signed in to change notification settings - Fork 3
Description
A match morphism triggers an event to happen in the future. There is some ambiguity about what it means for that match to be "still existing" when that time comes around and it's time to fire the event. The current logic is very strict about this: there needs to exist a morphism
Another example involves a door with a boolean attribute saying whether or not it's closed. Someone may be triggered to go through the door soon if the door is open, and if the door closes but reopens in the intervening time, we may wish that to be equivalent to the door having stayed open the whole time, rather than the clock deactivating when it closes and then being resampled when it reopens.
The right data for this is a subobject
The current behavior would be that @acset_colim, the representables that are explicitly mentioned are great candidates for what belongs to
Note: this change can only be made within AlgebraicRewriting.Incremental