unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Joshua Branson via "Bug reports for GUILE, GNU's Ubiquitous Extension Language" <bug-guile@gnu.org>
To: 51445@debbugs.gnu.org
Subject: bug#51445: (no subject)
Date: Wed, 27 Oct 2021 15:18:38 -0400	[thread overview]
Message-ID: <87r1c6z375.fsf@dismail.de> (raw)

This is more of a feature request.  Apologies if this is an annoying
request.

So I made a pretty noobie-like mistake a few days ago using (guix
records).  When one tries to create a <record-configuration>, he
invariably creates an infinite number of records.  The guile compiler
eventually runs out of memory and stops compiling with an error
message like:

fish: Job 1, 'guile break-guile-compiler.scm' terminated by signal SIGKILL (Forced quit)

I submitted this "bug" report to bug-guix@gnu.org as well.

http://issues.guix.gnu.org/51383

It probably will not be fixed at the (guix records) macro level
anytime soon, so I am submitting it here in case guile developers are
interested in improving their compiler error messages.  I came across
this compiler error while debugging my 1,000 line program.  Trying to
figure out what was wrong without any hints from appropriate error
messages was slightly confusing.

Here is the bad code:

(use-modules (guix records))

(define-record-type* <record-configuration>
  record-configuration make-record-configuration
  record-configuration?

  (command record-configuration-command
    ;; the error is here is on the next line
    (default (record-configuration))))  

(record-configuration)


Thanks,
Joshua





                 reply	other threads:[~2021-10-27 19:18 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=87r1c6z375.fsf@dismail.de \
    --to=bug-guile@gnu.org \
    --cc=51445@debbugs.gnu.org \
    --cc=jbranso@dismail.de \
    /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).