a6811f2ba5
The `add-endpoint!` call is changed in two ways: - the old `assertion-fn` has become `update-fn`, yielding both an assertion *and* an optional handler, because if the handler depends on a field which changes, previously the handler wasn't being updated - a new parameter, `dynamic?`, can be set to #f (it's usually #t) to ensure that the assertion and skeleton-interest are calculated only once ever, and are not connected to the dataflow machinery. The first change makes it possible for the `(later-than (deadline))` pattern, where `deadline` is a field, to work; the second change makes `during` and `during/spawn` work correctly in the face of field updates. |
||
|---|---|---|
| .. | ||
| abandon-actions-on-exn.rkt | ||
| correct-retraction-on-exn.rkt | ||
| double-cross-layer.rkt | ||
| during-criterion-snapshotting.rkt | ||
| partial-retraction.rkt | ||
| responsibility-transfer-1.rkt | ||
| responsibility-transfer-2.rkt | ||
| simple-addition.rkt | ||
| simple-box-and-client.rkt | ||
| simple-cross-layer.rkt | ||