From: Lars Ingebrigtsen <larsi@gnus.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 42644@debbugs.gnu.org
Subject: bug#42644: 28.0.50; Please let max and min accept zero arguments
Date: Sat, 12 Feb 2022 09:09:40 +0100 [thread overview]
Message-ID: <878rug4ibf.fsf@gnus.org> (raw)
In-Reply-To: <87tuxmkhd9.fsf@web.de> (Michael Heerdegen's message of "Sat, 01 Aug 2020 08:30:42 +0200")
Michael Heerdegen <michael_heerdegen@web.de> writes:
> I want to suggest to make the functions `max' and `min' accept zero
> arguments, with
>
> (max) => negative infinity
> (min) => positive infinity
>
> That would be mathematically consistent, and would offer an easier to
> remember syntax to specify the infinities (at least for mathematicians).
> I hate the read syntax suggested in the manual, I have to look it up
> every single time. Ironically, most of the time I use it it's the
> initial value for a max or min number sequence folding.
I think the conclusion here was that there was limited enthusiasm for
doing this (since it's more likely that (max) is a programming error
instead of a way to write -1.0e+INF). And there didn't seem to be much
enthusiasm for defining constants for this, either, since we have the
1.0e+INF syntax, as hard as that is to type.
So I'm closing this bug report.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2022-02-12 8:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-01 6:30 bug#42644: 28.0.50; Please let max and min accept zero arguments Michael Heerdegen
2020-08-01 10:02 ` Stefan Kangas
2020-08-01 10:21 ` Andy Moreton
2020-08-01 10:21 ` Mattias Engdegård
2020-08-01 16:31 ` Drew Adams
2020-08-01 23:34 ` Michael Heerdegen
2020-08-02 4:02 ` Lars Ingebrigtsen
2020-08-02 6:43 ` Dmitry Alexandrov
2020-08-03 2:08 ` Michael Heerdegen
2020-08-03 11:05 ` Stefan Kangas
2020-08-03 17:11 ` Dmitry Alexandrov
2022-02-12 8:09 ` Lars Ingebrigtsen [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878rug4ibf.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=42644@debbugs.gnu.org \
--cc=michael_heerdegen@web.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.