unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Daniel Colascione <dancol@dancol.org>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: make-vector documentation is wrong
Date: Thu, 14 May 2020 19:46:09 -0700	[thread overview]
Message-ID: <5bcc3508-9d65-c5b4-255e-898f8e1dc3c1@cs.ucla.edu> (raw)
In-Reply-To: <0430a770-2bb8-2d46-9b28-420c8a6e0a24@dancol.org>

On 5/14/20 6:36 PM, Daniel Colascione wrote:
> We should fix either the docstring or the behavior
> of make-vector, and the latter seems better to me because it reduces the number
> of special cases in the system.

That depends on how one counts special cases.

(make-string 0 0), (make-list 0 0), (vector), and (list) all have the property
that (make-vector 0 0) does - that is, each call returns the same empty object
each time. I imagine that make-vector was implemented to be consistent with the
other functions - at least, this behavior appears to be a conscious decision
rather than accidental. So it may make sense to change these functions'
documentation instead of their implementation's longstanding behavior.



  reply	other threads:[~2020-05-15  2:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-15  1:36 make-vector documentation is wrong Daniel Colascione
2020-05-15  2:46 ` Paul Eggert [this message]
2020-05-15  2:59   ` Daniel Colascione
2020-05-15  3:19     ` Paul Eggert
2020-05-15  3:41   ` Stefan Monnier
2020-05-15  6:34     ` Paul Eggert
2020-05-15  9:58       ` Eli Zaretskii
2020-05-15  6:49   ` Eli Zaretskii

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/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5bcc3508-9d65-c5b4-255e-898f8e1dc3c1@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=dancol@dancol.org \
    --cc=emacs-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/emacs.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).