all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Josselin Poiret <dev@jpoiret.xyz>
Cc: Andreas Enge <andreas@enge.fr>,  guix-devel@gnu.org
Subject: Re: Syntax and gexp for ff5f34ae757d709987896d6164bf125319a0f764
Date: Fri, 31 Mar 2023 10:02:58 -0400	[thread overview]
Message-ID: <87tty1vx0t.fsf@gmail.com> (raw)
In-Reply-To: <87cz4ps5hr.fsf@jpoiret.xyz> (Josselin Poiret's message of "Fri,  31 Mar 2023 10:13:36 +0200")

Hi Josselin,

Josselin Poiret <dev@jpoiret.xyz> writes:

> Hi Maxim,
>
> Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:
>
>> I've seen this too, but it disappears if you byte-compile the project.
>> I'm not sure what that means, although it does seems sub-optimal that we
>> rely on byte-compilation for the code to evaluate correctly.
>
> The problem actually comes from stale byte-compiled files.  If you were
> to interpret everything, it would work properly.  The issue is when a
> variable becomes a syntax-transformer, ie. a macro: then it should get
> expanded at compile-time, but guile doesn't recompile dependents
> (because it doesn't know about them).  Hence, in dependent .go files,
> the variable didn't get expanded, and is then used at runtime, hence the
> error.

I thought I had cleared all .go files, but your explanation suggests I
didn't.  I probably got confused in my multiple sessions on various
machines :-).

Thanks for the explanation.

-- 
Thanks,
Maxim


      parent reply	other threads:[~2023-03-31 14:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-30 10:51 Syntax and gexp for ff5f34ae757d709987896d6164bf125319a0f764 Andreas Enge
2023-03-30 18:49 ` Josselin Poiret
2023-03-30 23:19   ` Leo Famulari
2023-03-31  8:15     ` Josselin Poiret
2023-04-01 16:13       ` Leo Famulari
2023-03-31  2:12 ` Maxim Cournoyer
2023-03-31  8:13   ` Josselin Poiret
2023-03-31  8:42     ` Andreas Enge
2023-03-31 14:02     ` Maxim Cournoyer [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=87tty1vx0t.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=andreas@enge.fr \
    --cc=dev@jpoiret.xyz \
    --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.