Just a spelling fix - Staffan Tjernstrom

 

From: SG14 [mailto:sg14-bounces@lists.isocpp.org] On Behalf Of Michael Wong via SG14
Sent: Thursday, 09 January, 2020 20:05
To: Matthew Bentley <mattreecebentley@gmail.com>
Cc: Michael Wong <fraggamuffin@gmail.com>; Low Latency:Game Dev/Financial/Trading/Simulation/Embedded Devices <sg14@lists.isocpp.org>
Subject: Re: [SG14] Table of past, present and future SG14 proposals

 

HI all I need to collate an authors list before publishing this list of papers and issues by next Monday Jan 13. As I made this open for edit, everyone is anonymous so I don't know who actually edited what. So here is an authors list that I am guessing at. Please append your name if you made an edit and want to be a co-author. There is no limit.

Ben Craig, Paul Bendixen, Matthew Bentley, Inbal Levi, Rene Riviera, Steffan TJ

 

Also please correct me if I misspelled the name. Thanks.

 

On Wed, Jan 8, 2020 at 7:15 PM Michael Wong <fraggamuffin@gmail.com> wrote:

Hi Matthew, yes please feel free to correct and add any domain you wish. Thank you and nice catch.

 

On Wed, Jan 8, 2020 at 7:07 PM Matthew Bentley <mattreecebentley@gmail.com> wrote:

Thanks Michael-
guessing "PTF Colony" was meant to be "PLF Colony", but could simply
be renamed "Colony" as plf is just the namespace for my work.

Are we listing SG14 domains of work only? If not, there's a few more
domains which can be added to colony as mentioned in the introduction
to that paper.
Cheers-
M

On 09/01/2020, Michael Wong via SG14 <sg14@lists.isocpp.org> wrote:
> Thanks Paul, I agree. Please add that and I will augment it with direct
> links.
>
> Great catch!
>
> On Wed, Jan 8, 2020 at 4:46 PM Paul M. Bendixen via SG14 <
> sg14@lists.isocpp.org> wrote:
>
>> Looks good, though I'd remark that the ring_span proposal would also
>> be very useful in the embedded domain.
>> /Paul
>>
>> Den ons. 8. jan. 2020 kl. 17.51 skrev Michael Wong via SG14
>> <sg14@lists.isocpp.org>:
>> >
>> > Hi all, as promised from the December's SG14 survey of Domain features,
>> I have started building a google spread sheet of features, issues,
>> defects
>> we wish to address. We discussed some of these wishlist during the call
>> and
>> thanks to Steffan TJ's post-call discussion, we collated further
>> propoals.
>> We can put this into github after we had some discussions.
>> >
>> > This is my recollection of current status, though I may be wrong in
>> > many
>> entries so I am hoping others, especially the authors can correct this,
>> directly by editing the document.
>> >
>> > The goal of this is to use this to record our past succecssful
>> proposals, and also to drive additional proposals of interest. Some of
>> the
>> proposals does not need to be directly related to SG14, but could be in
>> led
>> through other groups (such as SG6, SG19) but we we are also watchign it
>> for
>> interest.
>> > If you want editing, just ask me. As it is Google, obviously google
>> accounts works best, but non-google account sometimes also work, though I
>> have not detected what the patterns are.
>> >
>> > I hope to turn this into a regular status document update for the
>> mailing on SG14 progress.
>> >
>> >
>> https://docs.google.com/spreadsheets/d/1JnUJBO72QVURttkKr7gn0_WjP--P0vAne8JBfzbRiy0/edit#gid=0
>> >
>> >
>> > _______________________________________________
>> > SG14 mailing list
>> > SG14@lists.isocpp.org
>> > https://lists.isocpp.org/mailman/listinfo.cgi/sg14
>>
>>
>>
>> --
>> • − − •/• −/• • −/• − • •/− • • •/•/− •/− • •/• •/− • • −/•/− •/• − −
>> •− •/− − •/− −/• −/• •/• − • •/• − • − • −/− • − •/− − −/− −//
>> _______________________________________________
>> SG14 mailing list
>> SG14@lists.isocpp.org
>> https://lists.isocpp.org/mailman/listinfo.cgi/sg14
>>
>




IMPORTANT: The information contained in this email and/or its attachments is confidential. If you are not the intended recipient, please notify the sender immediately by reply and immediately delete this message and all its attachments. Any review, use, reproduction, disclosure or dissemination of this message or any attachment by an unintended recipient is strictly prohibited. Neither this message nor any attachment is intended as or should be construed as an offer, solicitation or recommendation to buy or sell any security or other financial instrument. Neither the sender, his or her employer nor any of their respective affiliates makes any warranties as to the completeness or accuracy of any of the information contained herein or that this message or any of its attachments is free of viruses.