unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Using #true and #false everywhere?
Date: Tue, 20 Oct 2020 14:45:54 +0200	[thread overview]
Message-ID: <CAJ3okZ3zTdo4aNSbGtOzFgSO2h+B5M9hmR3aUmq2-g6eq4LPMg@mail.gmail.com> (raw)
In-Reply-To: <20201020103244.GB6805@jurong>

Hi Andreas,

On Tue, 20 Oct 2020 at 12:33, Andreas Enge <andreas@enge.fr> wrote:

> And since we are on the bikeshedding front, I feel like writing a second
> message.

You are playing the devil's lawyer role, right?


> On Fri, Oct 16, 2020 at 12:38:23PM +0200, Ludovic Courtès wrote:

> - The "non-typedness of booleans": Does "(if 1 2 3)" raise an exception or
>   work, and if the latter is true, what is the result? And if I replace
>   "1" by "0" or the empty list? (In Guix, this is related to the question:

This is a question about the standard, right?  It is not about #true
or #false vs #t or #f.

>   Do I need to add #t or #f at the end of a phase, or is the value of its
>   last statement sufficient?)

The question is how to know the value of the last statement.  And it
is Scheme/Guile question, right?  Not really about the #true vs #t,
isn't it?


> - What are the different procedures for comparing things?

The Guile manual explains well, isn't it?

<https://www.gnu.org/software/guile/manual/html_node/Equality.html>


Cheers,
simon

ps:
Well, one example showing all the points is, IMHO:

--8<---------------cut here---------------start------------->8---
scheme@(guix-user)> (define (f x) (when (> x 2) #true))
scheme@(guix-user)> (map f '(1 2 3 4))
$1 = (#<unspecified> #<unspecified> #t #t)
--8<---------------cut here---------------end--------------->8---

(whatever the comparison (> x 2) is; could be package related.)


  parent reply	other threads:[~2020-10-20 12:46 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
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 [this message]
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=CAJ3okZ3zTdo4aNSbGtOzFgSO2h+B5M9hmR3aUmq2-g6eq4LPMg@mail.gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=andreas@enge.fr \
    --cc=guix-devel@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.
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).