All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Williams <patrick@stwcx.xyz>
To: Richard Hanley <rhanley@google.com>
Cc: "Khetan, Sharad" <sharad.khetan@intel.com>,
	"OpenBMC Maillist" <openbmc@lists.ozlabs.org>,
	"Adrian Ambrożewicz" <adrian.ambrozewicz@linux.intel.com>
Subject: Re: Upstream Yocto Bringing in GCC 10
Date: Tue, 2 Jun 2020 17:55:01 -0500	[thread overview]
Message-ID: <20200602225501.GJ17541@heinlein> (raw)
In-Reply-To: <CAH1kD+aCKNRY4sxPL0bwt0pzL+jW7QBmn7-_PTManZnn08kijg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 923 bytes --]

On Tue, Jun 02, 2020 at 03:12:32PM -0700, Richard Hanley wrote:
> Does anyone have an idea of what a good test project would be? Something of
> modest size that we can look for any hidden dragons that still need taming.

I'm starting work on adding coroutine support to sdbusplus as an
alternative to Boost::ASIO.  I think it would be also interesting to
look at sdeventplus for adding coroutine support and hopefully some
convergance between the two of them to facilitate coroutine reuse
(especially in the top-level scheduling portions).

My main motivations are:
    - Simplifying / flattening the callback lambdas associated with ASIO
      by using coroutines instead.

    - Use sdbusplus-coroutines as the basis for generating client
      bindings.  Since the project is moving towards async applications,
      there isn't much value in investing in sync client bindings.

-- 
Patrick Williams

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2020-06-02 22:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-17 17:19 Upstream Yocto Bringing in GCC 10 Andrew Geissler
2020-05-18  0:08 ` Patrick Williams
2020-05-22  0:36   ` Andrew Geissler
2020-05-25 12:35     ` Adrian Ambrożewicz
2020-05-26 12:33       ` Brad Bishop
2020-05-26 15:57       ` Patrick Williams
2020-06-02  8:18         ` Adrian Ambrożewicz
2020-06-02 18:32           ` Khetan, Sharad
2020-06-02 20:09             ` Patrick Williams
2020-06-02 22:12               ` Richard Hanley
2020-06-02 22:55                 ` Patrick Williams [this message]
2020-06-02 23:02                   ` William Kennington

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200602225501.GJ17541@heinlein \
    --to=patrick@stwcx.xyz \
    --cc=adrian.ambrozewicz@linux.intel.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=rhanley@google.com \
    --cc=sharad.khetan@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.