I can imagine this being yet another item in the long line of “needs executors”, or at least some kind of message loop. Also, I’ll suggest this be coined “interactive input”, so that touchscreens and game pads get lumped in, while files
and networks get excluded.
From: SG14 <firstname.lastname@example.org> On Behalf Of
Guy Cpp via SG14
Sent: Friday, January 3, 2020 11:40 AM
Cc: Guy Cpp <email@example.com>
Subject: [EXTERNAL] Re: [SG14] Jan 8 SG14 monthly call
I would like to canvas opinion about my next large paper, which is about host notification (keyboard input, mouse input, that sort of thing). I appreciate I don't actually have a paper so it should go low down the priority list, but I would
like to kick off a discussion about this before going to SG13,
Looks interesting Ben, but
would also be useful (for those of us not clued in) to have a brief explanation in that paper about how just using custom allocators won't fix the explicit problem of allocation not being ideal for each platform.
SG14 mailing list