From: Maxime Devos <maximedevos@telenet.be>
To: guile-devel@gnu.org, guix-devel@gnu.org
Subject: A lexical use-modules?
Date: Sat, 26 Mar 2022 20:21:07 +0100 [thread overview]
Message-ID: <c316f1438a6647d4ced2e13b8fac97b5de3b7bcc.camel@telenet.be> (raw)
[-- Attachment #1: Type: text/plain, Size: 1539 bytes --]
Hi,
[ CC'ing guix-devel@ because this functionality could be useful in Guix
package definitions ]
Currently, use-modules cannot be meaningfully used inside procedures,
unless '(current-module)' is always the module in which the procedure
is defined.
I wondered if some kind of 'lexical use-modules' was possible, with
sufficient macroology and module reflection, and it looks like it is:
(use-modules (srfi srfi-1))
(define-syntax use-module/lexical
;; todo: integrate into (use-modules ...)?
(lambda (s)
(syntax-case s ()
((_ foo)
(let* ((module-name (syntax->datum #'foo))
(interface (resolve-interface module-name)))
(define (binding->import name variable)
(define name-syntax (datum->syntax s name))
#`(define-syntax #,name-syntax (identifier-syntax (@ foo
#,(datum->syntax #'irrelevant name)))))
#`(begin #,@(module-map binding->import interface)))))))
(define &exception 'top-level)
(let ()
(use-module/lexical (ice-9 exceptions))
(pk 'inner &exception raise-continuable))
;;; (inner #<record-type &exception> #<procedure raise-continuable (obj)>)
(pk 'outer &exception)
;;; (outer top-level)
(pk 'unbound-variable raise-continuable)
;; a backtrace!
Limitation: things like
(define (foo)
(use-module/lexical (platform-specific-constants))
(if on-linux?
CONSTANT_ONLY_DEFINED_ON_LINUX
CONSTANT_ONLY_DEFINED_ON_HURD))
won't work in cross-compilation contexts.
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next reply other threads:[~2022-03-26 19:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-26 19:21 Maxime Devos [this message]
[not found] ` <CAGua6m33_=0=B9jaL4Jw7yP=yycD0eFxiAMK62iVBPuUV8F2wg@mail.gmail.com>
[not found] ` <4fb1eef748667d5e33d9df674af77ff52d30cd00.camel@telenet.be>
[not found] ` <CAGua6m1eNt5ABwDGT_3ifwCjT5YQkpd8W5XBjgwYGZE2B8WW0g@mail.gmail.com>
2022-03-27 10:40 ` A lexical use-modules? Maxime Devos
[not found] ` <CAGua6m0H1CZOpDtCUgX=+h6P+zT74_VEA8etQKKs5JwVGLurGQ@mail.gmail.com>
2022-03-27 15:11 ` Maxime Devos
2022-03-29 13:20 ` Ludovic Courtès
2022-03-29 14:59 ` Maxime Devos
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=c316f1438a6647d4ced2e13b8fac97b5de3b7bcc.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=guile-devel@gnu.org \
--cc=guix-devel@gnu.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 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).