From: "Ludovic Courtès" <ludo@gnu.org>
To: Maxime Devos <maximedevos@telenet.be>
Cc: iskarian@mgsn.dev, 50286@debbugs.gnu.org
Subject: [bug#50286] [RFC PATCH] Let 'package-location' returns location of surrounding 'let'.
Date: Mon, 06 Sep 2021 12:07:04 +0200 [thread overview]
Message-ID: <87o89681br.fsf@gnu.org> (raw)
In-Reply-To: <0b61652d751633f78e876a27be88ed14e47527b6.camel@telenet.be> (Maxime Devos's message of "Mon, 30 Aug 2021 23:26:43 +0200")
Hello,
Maxime Devos <maximedevos@telenet.be> skribis:
> These three patches allows (guix upstream) to replace the values in the surrounding 'let'
> form, if any. It's important for constructs like:
>
> (define-public gnash
> (let ((version "0.8.11")
> (commit "583ccbc1275c7701dc4843ec12142ff86bb305b4")
> (revision "0"))
> (package
> (name "gnash")
> (version (git-version version revision commit))
> (source (git-reference
> (url "https://example.org")
> (commit commit)))
> [...])))
>
> such that it can update the version, commit, revision. (Currently only the
> version will be updatable, but see <https://issues.guix.gnu.org/50072#0>
> and <https://issues.guix.gnu.org/50072#9> for work on making 'commit' updatable).
This is smart!
I wonder if we’re going overboard, though. Intuitively, I would rather
leave ‘location’ fields dumb, and instead add editing features to do
things like getting the location of the parent sexp. It does add some
overhead, but it also makes things more explicit and preserves
separation of concern. (Also, in ‘core-updates-frozen’,
‘go-to-location’ uses a location cache that makes it less expensive than
on ‘master’.) But yeah, it’s trickier…
Hmm, thinking out loud, what about this: use the same trick as you did,
but replace ‘define-public’ instead of ‘let’ & co., so as to be less
intrusive.
(define-syntax-parameter current-definition-location
(identifier-syntax #f))
(define-syntax define-public*
(syntax-rules ()
((_ prototype body)
(define-public prototype
(syntax-parameterize ((current-definition-location
(identifier-syntax (current-source-location))))
body)))))
Since there’s code that assumes ‘package-location’ returns the location
of the (package …) sexp, we could add a ‘definition-location’ field in
<package>, defaulting to ‘current-definition-location’, or tweak
‘location’ to include both.
WDYT?
Thanks,
Ludo’.
next prev parent reply other threads:[~2021-09-06 10:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-30 21:26 [bug#50286] [RFC PATCH] Let 'package-location' returns location of surrounding 'let' Maxime Devos
2021-09-06 10:07 ` Ludovic Courtès [this message]
2021-09-07 19:27 ` Ludovic Courtès
2021-09-07 20:15 ` Sarah Morgensen
2021-09-08 13:45 ` Ludovic Courtès
2021-09-07 20:30 ` Maxime Devos
2021-09-08 13:38 ` Ludovic Courtès
2021-09-13 10:37 ` bug#50286: " Ludovic Courtès
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o89681br.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=50286@debbugs.gnu.org \
--cc=iskarian@mgsn.dev \
--cc=maximedevos@telenet.be \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).