From: jbranso--- via "Bug reports for GUILE, GNU's Ubiquitous Extension Language" <bug-guile@gnu.org>
To: 46014@debbugs.gnu.org
Subject: bug#46014: (define (thunk) (lambda (x) x)) should be a compile error?
Date: Wed, 20 Jan 2021 21:04:47 -0500 [thread overview]
Message-ID: <87h7nb3v0g.fsf@dismail.de> (raw)
Hello!
Consider this bit of simple code:
#+BEGIN_SRC scheme
(define (thunk)
(lambda (x)
x))
(thunk) ;; works ok, I guess.
(thunk "hello world!\n") ;; runtime error
;;; <stdin>:1074:0: warning: possibly wrong number of arguments to `thunk'
ice-9/boot-9.scm:1669:16: In procedure raise-exception:
Wrong number of arguments to #<procedure thunk ()>
Entering a new prompt. Type `,bt' for a backtrace or `,q' to continue.
#+END_SRC
Guile will compile this program seemingly with no error. Guile will
correctly report at runtime that procedure '(thunk "hello world!\n")'
takes no arguments, but it's lambda accepts 1 argument. Would it be
possible to report this error at compile time? Would that be
advantageous?
I personally can consider one time where reporting this error at
compile time would be advantageous. Here's how I found out about this
error. (would ya'll call this an error/bug/feature)?
#+BEGIN_SRC scheme
(use-modules
(srfi srfi-9))
(define-record-type <lunch>
(make-lunch food duration location)
lunch?
(food lunch-food)
(duration lunch-duration)
(location lunch-location))
(define dine-out
(make-lunch "pizza" "30 min" "downtown"))
;; maybe this should be a syntax error instead of a runtime error?
(define (list-lunch)
(match-lambda (($ <lunch> food duration location )
(list food duration location))))
;; this is the proper way to do it.
(define list-lunch
(match-lambda (($ <lunch> food duration location )
(list food duration location))))
#+END_SRC
I eventually discovered what the issue was, but I had to run the code
to discover it.
I don't know if this is a silly bug report. If it is, sorry for the
noise.
Thanks,
Joshua
P.S. Guile's error messages at compile time and runtime are super
well written. Thanks!
next reply other threads:[~2021-01-21 2:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-21 2:04 jbranso--- via Bug reports for GUILE, GNU's Ubiquitous Extension Language [this message]
2021-01-21 13:56 ` bug#46014: (define (thunk) (lambda (x) x)) should be a compile error? Ricardo Wurmus
2021-01-21 18:16 ` Stefan Israelsson Tampe
2021-01-21 20:11 ` jbranso--- via Bug reports for GUILE, GNU's Ubiquitous Extension Language
2021-01-21 20:09 ` jbranso--- via Bug reports for GUILE, GNU's Ubiquitous Extension Language
2021-01-21 22:27 ` Ricardo Wurmus
2021-01-22 14:47 ` jbranso--- via Bug reports for GUILE, GNU's Ubiquitous Extension Language
2021-01-22 16:29 ` tomas
2021-01-23 15:02 ` Ricardo Wurmus
2021-01-23 15:17 ` jbranso--- via Bug reports for GUILE, GNU's Ubiquitous Extension Language
2021-01-23 17:23 ` Ricardo Wurmus
2021-01-23 15:07 ` bug#46014: closing the bug report...hopefully jbranso--- via Bug reports for GUILE, GNU's Ubiquitous Extension Language
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=87h7nb3v0g.fsf@dismail.de \
--to=bug-guile@gnu.org \
--cc=46014@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).