Use a/many (potentially contextual) keyword to denote atomic blocks, rather than making it a library feature. For example atomic do { ... }.
| SF | F | N | A | SA |
|---|---|---|---|---|
| 5 | 8 | 1 | 0 | 0 |
The proposed approach to TM generally seems acceptable, and would fit in a TM TS v2.
| SF | F | N | A | SA |
|---|---|---|---|---|
| 3 | 12 | 1 | 0 | 0 |
We'll see it again after discussing the particular keyword approach. LEWG should also see it to discuss library support guarantees, if any.
Hello atomic { EWG(); }Next week, August 5th at 8AM Pacific (3PM GMT), we'll have an EWG telecon on the transactional memory light TS:
- Hans posted links to the EWG reflector yesterday.
- The latest background and motivation paper will be in the coming mailing (it fixes a few minor issues from the previous version).
- The wording paper is extremely short.
Let's discuss it on the reflector first. I expect to hear questions on implementations, as well as use of contextual keyword versus other approaches.Here's the call-in information:
Zoom Meeting ID 735059607 Zoom Meeting Password template Zoom Meeting Room https://iso.zoom.us/j/735059607?pwd=d2tzRkZrTGY1c241R2prOVIrVnNXdz09 Zoom Meeting Automatic Phone-In US: +16699006833,,735059607# or +14086380968,,735059607# Zoom Meeting Phone Number US: +1 669 900 6833 International numbers available https://iso.zoom.us/u/acPWjSNM0