From: jbranso--- via "Bug reports for GUILE, GNU's Ubiquitous Extension Language" <bug-guile@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 46014@debbugs.gnu.org
Subject: bug#46014: (define (thunk) (lambda (x) x)) should be a compile error?
Date: Thu, 21 Jan 2021 15:09:50 -0500 [thread overview]
Message-ID: <87eeie2gs1.fsf@dismail.de> (raw)
In-Reply-To: <87bldil7fo.fsf@elephly.net> (Ricardo Wurmus's message of "Thu, 21 Jan 2021 14:56:43 +0100")
Ricardo Wurmus <rekado@elephly.net> writes:
> Hi,
>
>> 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?
>
> This is not a bug. What you call “thunk” here is a procedure that
> returns a procedure. That’s very common and is often done to delay
> evaluation.
>
> It is in fact an error to call the procedure “thunk” with an argument.
> It doesn’t matter that it happens to return a procedure that *can* take
> an argument. The procedure it returns is just like any other value,
> though, and isn’t inspected any further.
>
> That said, it is not true that Guile will compile this without a
> complaint. I dumped your code snippet in a file foo.scm and
> compiled it:
>
> guild compile foo.scm
> foo.scm:6:0: warning: wrong number of arguments to `thunk'
> wrote `/home/rekado/.cache/guile/ccache/3.0-LE-8-4.4/home/rekado/dev/gx/gwl/foo.scm.go'
>
> Isn’t that exactly what you’re asking for?
Gotcha. Thanks for explaining! I suppose what I meant to say is,
should guile refuse to compile the above? In other languages, like C I
suppose, writing a function simultaneous with one and two arguments
would refuse to compile. The compiler would make you fix the code.
Should guile do this as well?
When I look at
#+BEGIN_SRC scheme
(define (thunk)
(lambda (x)
x))
#+END_SRC
or
#+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 refuse to compile?
(define (list-lunch)
(match-lambda (($ <lunch> food duration location )
(list food duration location))))
#+END_SRC
My thought is, this is clearly a mistake. This person needs to change
the above code.
Thanks,
Joshua
P.S. I'm not a scheme expert. I'm only reporting this, because I
recently read a blog post about free software users rarely report
perceived issues. I'm just trying to be helpful. :) Thanks for the
speedy response time.
--
Joshua Branson (joshuaBPMan in #guix)
Sent from Emacs and Gnus
https://gnucode.me
https://video.hardlimit.com/accounts/joshua_branson/video-channels
https://propernaming.org
"You can have whatever you want, as long as you help
enough other people get what they want." - Zig Ziglar
next prev parent reply other threads:[~2021-01-21 20:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-21 2:04 bug#46014: (define (thunk) (lambda (x) x)) should be a compile error? jbranso--- via Bug reports for GUILE, GNU's Ubiquitous Extension Language
2021-01-21 13:56 ` 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 [this message]
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=87eeie2gs1.fsf@dismail.de \
--to=bug-guile@gnu.org \
--cc=46014@debbugs.gnu.org \
--cc=jbranso@dismail.de \
--cc=rekado@elephly.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.
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).