From: Pierre Neidhardt <mail@ambrevar.xyz>
To: swedebugia <swedebugia@riseup.net>, guix-devel <guix-devel@gnu.org>
Subject: Re: Quicklisp importer bug in tarball->extract->parse
Date: Sat, 27 Apr 2019 09:15:35 +0200 [thread overview]
Message-ID: <87o94rkjfs.fsf@ambrevar.xyz> (raw)
In-Reply-To: <3f6d08e3-56d4-bc34-944d-b1305b8af37b@riseup.net>
[-- Attachment #1: Type: text/plain, Size: 1444 bytes --]
swedebugia <swedebugia@riseup.net> writes:
> Hi
>
> Thanks a lot for taking the time to look at this.
>
> On 2019-04-11 16:31, Pierre Neidhardt wrote:
>> Hi!
>>
>> I've had time to look at it a little.
>>
>> If you want to debug, you can, for instance, put a breakpoint in
>> guess-requirements-from-source,
>
> How exactly do you do this?
See
--8<---------------cut here---------------start------------->8---
,help debug
--8<---------------cut here---------------end--------------->8---
from the Guile REPL.
In particular
--8<---------------cut here---------------start------------->8---
,break PROCEDURE
--8<---------------cut here---------------end--------------->8---
should do what you want.
> (memoize
> ...
`memoize' takes a procedure as argument, not an arbitrary expression.
For instance in the following
--8<---------------cut here---------------start------------->8---
(let ((mfoo (memoize foo)))
(mfoo 17)
(mfoo 17))
--8<---------------cut here---------------end--------------->8---
`foo' will be called only once.
You don't have to use `memoize' though, you can also store the value you
want in a local variable and check if it's set or not. We can always
refine the code later.
>> It seems that you are on the right track, great job!
>
> Thanks for the encouragement!
And thanks for giving this a shot! :)
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
prev parent reply other threads:[~2019-04-27 7:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-29 20:07 Quicklisp importer bug in tarball->extract->parse swedebugia
2019-04-03 8:46 ` Pierre Neidhardt
2019-04-11 14:31 ` Pierre Neidhardt
2019-04-11 15:07 ` Ricardo Wurmus
2019-04-11 15:27 ` Pierre Neidhardt
2019-04-27 6:26 ` swedebugia
2019-04-27 7:15 ` Pierre Neidhardt [this message]
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=87o94rkjfs.fsf@ambrevar.xyz \
--to=mail@ambrevar.xyz \
--cc=guix-devel@gnu.org \
--cc=swedebugia@riseup.net \
/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.