From: Bengt Richter <bokr@bokr.com>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Using #true and #false everywhere?
Date: Sun, 18 Oct 2020 04:22:03 +0200 [thread overview]
Message-ID: <20201018022203.GA10753@LionPure> (raw)
In-Reply-To: <875z785n95.fsf@gmail.com>
Hi,
On +2020-10-17 21:36:06 -0400, Maxim Cournoyer wrote:
> Hello Tobias,
>
> Tobias Geerinckx-Rice <me@tobias.gr> writes:
>
> > Maxim,
> >
> > Maxim Cournoyer 写道:
> >> I'd only agree to such a change if it's already been standardized in
> >> the
> >> RnRS as such
> >
> > Sure, I think that's implied. #true and #false are part of the
> > R7RS-small standard.
>
> Thanks, I couldn't find where that was defined. Now that you've pointed
> it to me, it's defined in section 6.3 Booleans:
>
> The standard boolean objects for true and false are written as #t and
> #f. Alternatively, they can be written #true and #false,
> respectively.
>
> > I don't know what Guile ‘is’, but it supports that part of the
> > standard. I don't think it implements any of the RnRS completely?
> > I've heard it said that Guile targets R5RS, but that was ages ago.
>
> info '(guile) Guile and Scheme' suggests it supports all of the R5RS,
> R6RS or R7RS standards, plus a bunch of srfi modules.
>
> With this cleared, I don't have an objection to the proposal, other than
> the other points I've mentioned earlier (to recall those points: I don't
> perceive much value in it and it'll make the 'git blame' output noisy).
>
> Thanks,
>
> Maxim
>
I am against editing legacy code to s/#t/#true/ and s/#f/#false/
For those who need it, why not an emacs mode to view whatever beautification they like?
Or a separate canonicalizer/prettyprinter filter that you could invoke by command line
or from any editor that can pipe thhrough filters?
ISTM any any editing of signed-off sources creates quality/security-control work for
developers who are too valuable to waste their time on non-fun.
Delegating such simple changes to newbie contributors doesn't avoid the oversight work
and potential security risk: a "whoops, that better be reverted" may open a door just
long enough for some exploitation -- or at least require the conscientious to think about
whether the whoops really could have been exploitable somehow.
I see a waste of developer time, that can be much better used.
My 2¢ :)
--
Regards,
Bengt Richter
next prev parent reply other threads:[~2020-10-18 2:22 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-16 10:38 Using #true and #false everywhere? Ludovic Courtès
2020-10-16 13:19 ` Maxim Cournoyer
2020-10-16 13:36 ` Tobias Geerinckx-Rice
2020-10-18 1:36 ` Maxim Cournoyer
2020-10-18 2:22 ` Bengt Richter [this message]
2020-10-19 20:45 ` zimoun
2020-10-21 9:56 ` Ludovic Courtès
2020-10-20 9:57 ` Andreas Enge
2020-10-21 9:59 ` Ludovic Courtès
2020-10-21 11:21 ` Andreas Enge
2020-10-21 15:52 ` Ludovic Courtès
2020-10-21 11:51 ` Roel Janssen
2020-10-16 16:24 ` Vagrant Cascadian
2020-10-16 23:45 ` Danny Milosavljevic
2020-10-20 10:32 ` Andreas Enge
2020-10-20 11:10 ` Ricardo Wurmus
2020-10-20 12:02 ` zimoun
2020-10-20 12:59 ` Tobias Geerinckx-Rice
2020-10-20 13:11 ` zimoun
2020-10-20 13:32 ` Tobias Geerinckx-Rice
2020-10-20 14:26 ` zimoun
2020-10-20 15:48 ` Taylan Kammer
2020-10-21 1:25 ` Mark H Weaver
2020-10-21 6:18 ` Ricardo Wurmus
2020-10-21 10:04 ` Ludovic Courtès
2020-10-20 12:45 ` zimoun
2020-10-20 12:55 ` Andreas Enge
2020-10-21 10:20 ` Ludovic Courtès
2020-10-24 18:29 ` Robin Templeton
-- strict thread matches above, loose matches on Subject: below --
2020-10-16 22:06 Miguel Ángel Arruga Vivas
2020-10-17 0:25 ` jbranso
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201018022203.GA10753@LionPure \
--to=bokr@bokr.com \
--cc=guix-devel@gnu.org \
--cc=maxim.cournoyer@gmail.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).