ab64f71766
Instead of having restriction-paths as an adjunct to a change, they're more propertly a part of each assertion itself. The new `skeleton.rkt` keeps an optional restriction-path with each assertion, treating it as distinct from its underlying assertion. The idea of not signalling changes in assertions that have a restriction-path mismatch stays. |
||
|---|---|---|
| .. | ||
| abandon-actions-on-exn.rkt | ||
| clean-adhoc-on-termination.rkt | ||
| correct-retraction-on-exn.rkt | ||
| double-cross-layer.rkt | ||
| during-criterion-snapshotting.rkt | ||
| nesting-confusion.rkt | ||
| partial-retraction.rkt | ||
| responsibility-transfer-1.rkt | ||
| responsibility-transfer-2.rkt | ||
| simple-addition.rkt | ||
| simple-box-and-client.rkt | ||
| simple-cross-layer.rkt | ||
| state-machine.rkt | ||