From: Jean Abou Samra <jean@abou-samra.fr>
To: Guile User <guile-user@gnu.org>
Subject: Re: Silencing compilation warnings when calling compiler explicitly
Date: Wed, 10 Aug 2022 18:14:29 +0200 [thread overview]
Message-ID: <95055d6c-26c8-b3e5-682d-43c685ed050a@abou-samra.fr> (raw)
In-Reply-To: <a471ae66-f354-ac96-33b2-8c627b4528b8@abou-samra.fr>
Le 10/08/2022 à 18:05, Jean Abou Samra a écrit :
> Le 10/08/2022 à 16:42, Jean Abou Samra a écrit :
>> I know that in Guile 3.0 I can do #:warning-level 0,
>> and it works,
>
> Correction: no, it does not work (not sure why I thought that).
>
>
> $ cat x.scm
> (use-modules (system base compile))
>
> (display
> (compile '(lambda (x)
> (case x
> ((5 5) 5)
> ((6) 6)))
> #:warning-level 0
> #:env (current-module)))
> $ guile3.0 x.scm
> [auto-compilation messages snipped]
> ;;; <unknown-location>: warning: duplicate datum 5 in clause ((5 5) 5)
> of case expression (case x ((5 5) 5) ((6) 6))
> #<procedure 555de3e97468 (x)>
The same problem exists when compiling code with 'guild compile',
which really looks like a bug, so I'm going to report it.
$ cat cased.scm
(case 5
((5 5) 5))
$ guild3.0 compile -W0 cased.scm
cased.scm:2:3: warning: duplicate datum 5 in clause ((5 5) 5) of case
expression (case 5 ((5 5) 5))
wrote `/[...]/cased.scm.go'
prev parent reply other threads:[~2022-08-10 16:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-10 14:42 Silencing compilation warnings when calling compiler explicitly Jean Abou Samra
2022-08-10 14:46 ` Jean Abou Samra
2022-08-10 16:05 ` Jean Abou Samra
2022-08-10 16:14 ` Jean Abou Samra [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
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=95055d6c-26c8-b3e5-682d-43c685ed050a@abou-samra.fr \
--to=jean@abou-samra.fr \
--cc=guile-user@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.
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).