On Tue, Jan 11, 2022 at 11:19 PM René Ferdinand Rivera Morell <grafikrobot@gmail.com> wrote:
Just an FYI that the P2300 LEWG meeting is happening right before this one. So if that goes long expect some to be late to this meeting.

On Tue, Jan 11, 2022 at 9:45 PM Michael Wong via SG14 <sg14@lists.isocpp.org> wrote:
Topic: SG14 Low Latency Monthly
This meeting is focused on Financial/low latency. But if time permits, we can also
discuss Patrice's WIP games pape, P2300, and Swift


Michael Wong is inviting you to a scheduled Zoom meeting.

Topic: SG14 monthly
Time: 2nd Wednesdays 02:00 PM Eastern Time 1900 UTC (US and Canada)
    Every month on the Second Wed,

Join from PC, Mac, Linux, iOS or Android:
    Password: 789626

Or iPhone one-tap :
    US: +12532158782,,93151864365# or +13017158592,,93151864365#
Or Telephone:
    Dial(for higher quality, dial a number based on your current location):
        US: +1 253 215 8782 or +1 301 715 8592 or +1 312 626 6799 or +1
346 248 7799 or +1 408 638 0968 or +1 646 876 9923 or +1 669 900 6833
 or 877 853 5247 (Toll Free)
    Meeting ID: 931 5186 4365
    Password: 789626
    International numbers available: https://iso.zoom.us/u/abRrVivZoD

Or Skype for Business (Lync):


1. Opening and introduction

ISO Code of Conduct

ISO patent policy.

IEC Code of Conduct:


WG21 Code of Conduct:


1.1 Roll call of participants

1.2 Adopt agenda

1.3 Approve minutes from previous meeting, and approve publishing
 previously approved minutes to ISOCPP.org

1.4 Action items from previous meetings

2. Main issues (125 min)

2.1 General logistics

Future meeting plans

 Jan 12, 2022 02:00 PM ET/1900 UTC: Finance/Low Latency
Feb 9, 2022 02:00 PM ET/1900 UTC: Games
Mar 9, 2022 02:00 PM ET/1900 UTC: Embedded

2.2 Paper reviews

Discussion on Loww Latency/Finance topics
LEWG 3.5 hours each day in the past 3 months
sender receiver and asio
one addon change to C++23 to forward to library,
still design decision discussions outstanding; need change to some of this to increase consensus
majority happy, but some improvement to the paper could improve consensus over 6 strongly against
some concerns: too much rush at end of release cycle, should this make C++ 23
P2300, differs sender vs typed sender(signature of receiver), and calls set value
1. non-typed senders  are going away, must have signature
2. tag_invoke forwards customization to a layered stack of receivers for example, the return value needs to satisfy the concept and the tag_invoke on the receiver needs to work; both these requirements need to be satisfied
3. environment introduced so receiver can be queried for its environment in the connect function, so you can ask received for its environment  to give properties like async wait state; can query the environemnt 
4. sender trait defines the type for the set value overloads so you can look at properties of receiver so you can query receiver for set value signature; also helper structs to help you construct the special way in which teh set value set down
against : due to rushing, any sender type erased sender; require set error channel to always forward eh ptr because set value can throw
receiver concept requires that set error handler handles eh ptr Eric is looking at it, could be a problem for asynchronous networking on a single thread? how will this support ISRsm should not be only error channel

PB tried implementing minimal parts of it and did not see eh ptr requirement
is it throw all caution to the wind to get this through

Matthew Bentley
Colony name is a point of contention
Hive is now in the lead
BS has some concern on the name? LEWG, aiming for 23
need this out of LEWG by mid year, as it will take 3-5 cycles in LWG

SP summarized Swift model using annotation model for concurrent safety, though it seems Swift is not specifically about that and this is more narrow 
 [[lock-free]], [[real-time]] [[no-alloc]] 
MW mentioned interest in RUST and C++ safety
JM ask if there are general purposed annotation models to indentify functions  with labels as being correct to the label
ST mentioned wrong defaults and the annotation burden
Another language to research.. https://www.ponylang.io/


Discussion about Games topics:

 P2388R1 - Minimum Contract Support: either Ignore or Check_and_abort

Patrice's WIP on Games issues.

Finance topics from July 14, 2021.



2.2.1 any other proposal for reviews?

Deterministic Exception for Embedded by James Renwick


SG14/SG19 features/issues/defects:


2.3 Domain-specific discussions

2.3.1 SIG chairs

   - Embedded Programming chairs: Ben Craig, Wouter van Ooijen and Odin    Holmes, John McFarlane

   - Financial/Trading chairs: Staffan TjernstrÃm
Carl Cooke, Neal Horlock, 
   - Games chairs: Rene Riviera, Guy Davidson and Paul Hampson, Patrice Roy

   - Linear Algebra chairs: Bob Steagall, Mark Hoemmen, Guy Davidson

2.4 Other Papers and proposals

2.5 Future F2F meetings:

2.6 future C++ Standard meetings:


3. Any other business
As well as look through papers marked "SG14" in recent standards committee
paper mailings:

Code and proposal Staging area
4. Review

4.1 Review and approve resolutions and issues [e.g., changes to SG's
working draft]

4.2 Review action items (5 min)

5. Closing process

5.1 Establish next agenda

5.2 Future meeting

Jan 12, 2022 02:00 PM ET/1900 UTC: Finance/Low Latency
Feb 9, 2022 02:00 PM ET/1900 UTC: Games GUY
Mar 9, 2022 02:00 PM ET/1900 UTC: Embedded
SG14 mailing list

-- René Ferdinand Rivera Morell
-- Don't Assume Anything  -- No Supone Nada
-- Robot Dreams - http://robot-dreams.net