From: Matt Rice <ratmice@gmail.com>
To: Tom Tromey <tromey@adacore.com>
Cc: Simon Farre via Gdb-patches <gdb-patches@sourceware.org>,
Simon Farre <simon.farre.cx@gmail.com>
Subject: Re: [PATCH v1] gdb/DAP Introduce new methods to to Pretty Printers
Date: Mon, 17 Jul 2023 21:53:21 +0000 [thread overview]
Message-ID: <CACTLOFqXSPbnT6pBQ13yg2ANAmO+qe8hAS2R9gyPr1ohG3N7Zw@mail.gmail.com> (raw)
In-Reply-To: <87jzv3o8ck.fsf@tromey.com>
On Thu, Jul 13, 2023 at 8:38 PM Tom Tromey via Gdb-patches
<gdb-patches@sourceware.org> wrote:
>
> Maybe one way out would be to define a new way to do pretty-printers,
> with a compatibility shim.
FWIW, there has been a bit of spit-balling within the rust community
about leveraging Debug trait implementations
within pretty printers, where what seemed to me like the obvious way
to leverage these was to compile Debug impls to wasm,
and write a python wrapper which calls into the wasm. I haven't
thought or looked into it too much to have considered any hurdles of
this approach really, but it would be nice if languages with wasm
toolchains could define/compile pretty printers in their own language,
since often they already exist for the purpose of runtime logging...
Seemed worth bringing up if we're spit-balling here too.
next prev parent reply other threads:[~2023-07-17 21:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-25 9:21 Simon Farre
2023-06-25 10:22 ` Eli Zaretskii
2023-07-13 20:38 ` Tom Tromey
2023-07-17 20:52 ` Simon Farre
2023-07-19 14:41 ` Tom Tromey
2023-07-17 21:53 ` Matt Rice [this message]
2023-07-18 18:52 ` Tom Tromey
2023-07-20 9:47 ` Simon Farre
2023-07-21 0:27 ` Matt Rice
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=CACTLOFqXSPbnT6pBQ13yg2ANAmO+qe8hAS2R9gyPr1ohG3N7Zw@mail.gmail.com \
--to=ratmice@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.farre.cx@gmail.com \
--cc=tromey@adacore.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).