Primitives for Contract-based SynchronizationContract-Based Synchronization • October 26th, 2018
Contract Type FiledOctober 26th, 2018In each At, the contracts ae are exposed under the ⊕. The consequences of these contracts are then demanded by a sum of fusex . We defer the definition of Be.
Primitives for Contract-based SynchronizationContract-Based Synchronization • May 17th, 2010
Contract Type FiledMay 17th, 2010where m is a fresh name resulting from the fusion. Note that the (pi)i∈I\J can no longer be deduced through fusion, since the variable z was “consumed” by the first fusion. The rough result is that ⊕i pi allows a subset of the (pi)i∈I to be demanded through fusion, after which the rest is no longer available.