Path: ...!weretis.net!feeder8.news.weretis.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Michael S <already5chosen@yahoo.com>
Newsgroups: comp.lang.c++,comp.lang.c
Subject: Re: Threads across programming languages
Date: Thu, 2 May 2024 00:05:24 +0300
Organization: A noiseless patient Spider
Lines: 30
Message-ID: <20240502000524.00006525@yahoo.com>
References: <GIL-20240429161553@ram.dialup.fu-berlin.de>
	<v0ogum$1rc5n$1@dont-email.me>
	<v0ovvl$1ur12$4@dont-email.me>
	<v0shru$2vrco$1@raubtier-asyl.eternal-september.org>
	<v0spra$31ds4$2@dont-email.me>
	<v0stev$325kv$2@raubtier-asyl.eternal-september.org>
	<v0svum$32o8h$2@dont-email.me>
	<v0t0ah$32qj6$2@raubtier-asyl.eternal-september.org>
	<v0u8q7$3c1r5$3@dont-email.me>
	<D3yYN.61545$TyYf.34181@fx15.iad>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Injection-Date: Wed, 01 May 2024 23:05:28 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="70ca8e92afe142bcf05ef1d82a035787";
	logging-data="3548778"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1/WA5+6VZ/kGgEIsRqecNIifdGr+wy6XLo="
Cancel-Lock: sha1:pHoeamMQSPAe2XWHlJ9sKXP+UpY=
X-Newsreader: Claws Mail 4.1.1 (GTK 3.24.34; x86_64-w64-mingw32)
Bytes: 2521

On Wed, 01 May 2024 21:00:19 GMT
scott@slp53.sl.home (Scott Lurndal) wrote:

> Lawrence D'Oliveiro <ldo@nz.invalid> writes:
> >On Wed, 1 May 2024 11:00:04 +0200, Bonita Montero wrote:
> > =20
> >> Am 01.05.2024 um 10:53 schrieb Lawrence D'Oliveiro:
> >>  =20
> >>> No async/await? Oh, they haven=C3=A2=E2=82=AC=E2=84=A2t added that to=
 C++--yet. =20
> >>=20
> >> No, Boost.ASIO is event driven with asynchronous callbacks in a
> >> foreign thread's context. =20
> >
> >Callbacks can be a clunky way of event handling, since they force
> >you to break up your logic sequence into discontinguous pieces. This
> >is why coroutines have become popular, since they keep the logic
> >flow together. =20
>=20
> Callbacks work just fine, as the logic for submitting a request
> is quite different from the logic for completing a request;  indeed,
> they more closely mirror the hardware interrupt that signals
> completion.
>=20
> I wouldn't call coroutines popular at all, outside of python
> generators.

My impression was that in golang world co-routines are relatively
popular. But I can be wrong about it.