From: Markus Armbruster <armbru@redhat.com>
To: John Snow <jsnow@redhat.com>
Cc: Damien Hedde <damien.hedde@greensocs.com>,
"Edgar E. Iglesias" <edgar.iglesias@xilinx.com>,
Mark Burton <mark.burton@greensocs.com>,
qemu-devel <qemu-devel@nongnu.org>,
Mirela Grujic <mirela.grujic@greensocs.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: RFC: QMP configuration - allocating/setting qdev array properties?
Date: Tue, 25 Jan 2022 07:38:24 +0100 [thread overview]
Message-ID: <87lez45nhb.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <CAFn=p-Y1um_4k33XRPshWy6QjvMGvhq_tfR+s8EFBTFwhkBnrQ@mail.gmail.com> (John Snow's message of "Mon, 24 Jan 2022 14:09:01 -0500")
John Snow <jsnow@redhat.com> writes:
> On Wed, Jan 19, 2022 at 5:12 AM Markus Armbruster <armbru@redhat.com> wrote:
[...]
>> Another stop gap solution could be making QDict iterate in insertion
>> order, like Python dict does since 3.6.
>>
>
> I like this idea, I think. Are there any possible downsides here?
> Making the order more 'stable' in one regard might lead to people
> trusting it "too often" if there are other implementation details that
> might impact the order ... but I don't actually have any examples
> handy for that. It's just my fear.
For what it's worth, it took Python just one release cycle to overcome
this fear :)
prev parent reply other threads:[~2022-01-25 7:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-11 16:54 RFC: QMP configuration - allocating/setting qdev array properties? Mirela Grujic
2022-01-12 9:47 ` Damien Hedde
2022-01-19 10:12 ` Markus Armbruster
2022-01-24 19:09 ` John Snow
2022-01-25 6:38 ` Markus Armbruster [this message]
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=87lez45nhb.fsf@dusky.pond.sub.org \
--to=armbru@redhat.com \
--cc=damien.hedde@greensocs.com \
--cc=edgar.iglesias@xilinx.com \
--cc=jsnow@redhat.com \
--cc=mark.burton@greensocs.com \
--cc=mirela.grujic@greensocs.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/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.