From: ludo@gnu.org (Ludovic Courtès)
To: Alex Kost <alezost@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] emacs: Add completions for '--type' option of 'refresh' popup.
Date: Sun, 01 Nov 2015 18:18:54 +0100 [thread overview]
Message-ID: <87a8qx4ozl.fsf@gnu.org> (raw)
In-Reply-To: <87611mlr33.fsf@gmail.com> (Alex Kost's message of "Sat, 31 Oct 2015 23:29:20 +0300")
Alex Kost <alezost@gmail.com> skribis:
> Ludovic Courtès (2015-10-29 23:14 +0300) wrote:
[...]
>> You could use #:autoload, but only for ‘%updaters’ because
>> ‘upstream-updater-name’ is a macro so it needs to be available at
>> expansion time.
>
> I looked at (info "(guile) Using Guile Modules") and it has the following:
>
> An autoload is a good way to put off loading a big module
> until it’s really needed, for instance for faster startup or
> if it will only be needed in certain circumstances.
>
> ‘@’ can do a similar thing (see Using Guile Modules), but
> in that case an ‘@’ form must be written every time a binding
> from the module is used.
>
> To me it sounds like ‘@’ does the same thing as ‘#:autoload’, no?
I guess I was confused. A simple example confirms what the manual
explains:
--8<---------------cut here---------------start------------->8---
$ guild compile t.scm
wrote `/home/ludo/.cache/guile/ccache/2.0-LE-8-2.0/home/ludo/src/guix/t.scm.go'
$ guile t.scm
$ cat t.scm
(define (foo)
(@ (asdfasdfa) sdfsf))
--8<---------------cut here---------------end--------------->8---
> Also #:autoload should be used inside (define-module ...), but
> ‘guix-main.scm’ does not define a module.
Oh, right, I had overlooked that.
So yes, you can go ahead with your initial approach.
Thanks, and sorry for the confusion!
Ludo’.
next prev parent reply other threads:[~2015-11-01 17:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-28 18:55 [PATCH] emacs: Add completions for '--type' option of 'refresh' popup Alex Kost
2015-10-29 20:14 ` Ludovic Courtès
2015-10-31 20:29 ` Alex Kost
2015-11-01 17:18 ` Ludovic Courtès [this message]
2015-11-02 13:01 ` Alex Kost
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=87a8qx4ozl.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=alezost@gmail.com \
--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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
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.