--nextPart2452704.8O0MPIRh1q Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; protected-headers="v1" From: Kevin Ottens To: kde-core-devel@kde.org Cc: Jonah =?ISO-8859-1?Q?Br=FCchert?= Subject: Re: Croutons in kdereview Date: Wed, 27 Oct 2021 17:05:52 +0200 Message-ID: <2312360.4GJ5rmlQXz@wintermute> In-Reply-To: <1fb67601-475e-f796-4eff-436bd0cb0c17@kaidan.im> References: <1fb67601-475e-f796-4eff-436bd0cb0c17@kaidan.im> Hello, I don't think Jonah's question got an answer. If it did somehow it didn't s= how=20 up in my mail client and my apologies in advance. :-) In any case I've been wondering exactly the same thing. I'm asking because = the=20 fate of libraries like QCoro and Croutons would be to end up in KDE Framewo= rks=20 at some point (at least would make sense to me). It'd be odd to have two=20 overlapping libraries like this. Regards. On Monday, 30 August 2021 13:10:35 CEST Jonah Br=FCchert wrote: > Hi Janet, >=20 > I know I have asked this earlier already, but what is the relationship > between your library and QCoro? >=20 > Especially now that we are starting to use QCoro in some KDE projects > (namely spacebar and plasma-dialer), it would be really unfortunate if > they are not compatible. >=20 > The scope of both libraries seems to largely overlap, except for the > future type that can be passed to JavaScript, which I think is something > that QCoro is missing. >=20 >=20 > I hope this hasn't been asked already on this list, but I tried to check > all replies I could find. >=20 >=20 > Thanks, >=20 > Jonah >=20 > Am 29.08.21 um 05:10 schrieb Janet Blackquill: > > Hello, > >=20 > > https://invent.kde.org/libraries/croutons is in kdereview now > >=20 > > Croutons is a library containing assorted functionality for dealing > > with asynchronous code in Qt, most notably a future type that can be > > passed into QML as a JavaScript Thennable (similarly to Qt IVI's > > PendingReply) and headers for C++20 coroutine integration for the > > Croutons Future types + some Qt types that make sense to co_await. > >=20 > > The library is largely headers-only, sans the FutureBase, which has > > one (1) associated source file needing to be compiled into a binary. > >=20 > > -- Janet =2D-=20 Kevin Ottens, http://ervin.ipsquad.net enioka Haute Couture - proud patron of KDE, https://hc.enioka.com/en --nextPart2452704.8O0MPIRh1q Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. Content-Transfer-Encoding: 7Bit -----BEGIN PGP SIGNATURE----- iF0EABECAB0WIQQXFmpSdcX6bxpI/XgHS7vLjezJ4gUCYXlq0AAKCRAHS7vLjezJ 4qUbAKCY3puTV2Pd4EuZDTDI0qU7LVl+OwCfaf/w9X8XUSECfnbOWm5go0TEsL4= =lRIL -----END PGP SIGNATURE----- --nextPart2452704.8O0MPIRh1q--