From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Jean Abou Samra <jean@abou-samra.fr>, guile-devel@gnu.org
Subject: Re: Macro for Python-style debugging output
Date: Wed, 30 Mar 2022 21:08:12 +0200 [thread overview]
Message-ID: <a14bf97b7a90f7d7e76df6cb34cb37ec7a9ff00d.camel@gmail.com> (raw)
In-Reply-To: <8bfae8ae-3965-1fc7-1ab0-d67b1c87a831@abou-samra.fr>
Am Montag, dem 28.03.2022 um 21:22 +0200 schrieb Jean Abou Samra:
> The following macro is a variant of peek that mimics Python's =
> format specifier (e.g. print(f"{a=} {a+b=}")) by printing expressions
> and the values they evaluate to.
>
> (define-syntax-rule (db arg ...)
> (begin
> (let ((evaluated-arg arg))
> (format (current-error-port) ";;; ~s => ~s\n" (quote arg)
> evaluated-arg)
> evaluated-arg)
> ...))
>
> Am I reinventing the wheel? Does anyone see value in this
> being added to Guile?
I think using plain old 'peek' might be preferable in most cases.
While you're missing out on the LHS expression, you can mix it with
symbols arbitrarily, e.g. (peek 'my-function a b 'args+kwargs= rest)
Cheers
next prev parent reply other threads:[~2022-03-30 19:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-28 19:22 Macro for Python-style debugging output Jean Abou Samra
2022-03-30 19:08 ` Liliana Marie Prikler [this message]
2022-03-31 2:38 ` Thien-Thi Nguyen
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a14bf97b7a90f7d7e76df6cb34cb37ec7a9ff00d.camel@gmail.com \
--to=liliana.prikler@gmail.com \
--cc=guile-devel@gnu.org \
--cc=jean@abou-samra.fr \
/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).