From: Juanma Barranquero <lekktu@gmail.com>
To: Adam Porter <adam@alphapapa.net>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: master a6b5985: Avoid duplicated character classes in rx
Date: Tue, 10 Dec 2019 07:32:01 +0100 [thread overview]
Message-ID: <CAAeL0ST7BnTWCCRAdbHvnUqY6Kh1HFXuJfzSdsfWzPQqiHZn5A@mail.gmail.com> (raw)
In-Reply-To: <87y2vksvut.fsf@alphapapa.net>
[-- Attachment #1: Type: text/plain, Size: 877 bytes --]
On Tue, Dec 10, 2019 at 4:28 AM Adam Porter <adam@alphapapa.net> wrote:
> There are hundreds of thousands, probably millions, of lines of Elisp in
> third-party packages and user configurations in the world. Removing the
> return value of `push' would be a breaking change affecting innumerable
> users.
Just for the record, our sources have approx. 1,345,500 non-empty,
non-comment lines of lisp. I found 34 uses of the return value of push
(could be a few more that I didn't find, but not many).
That's one use every ~40,000 lines of code, or approx 0,0025% of them.
If code outside has a similar rating, breaking it wouldn't be really
something that should kept us awake.
But anyway, the point is moot, as non-documenting it just means that the
code is mistaken, and will continue to be so. As Stefan as said, nobody
was talking about modifying push's implementation.
[-- Attachment #2: Type: text/html, Size: 1301 bytes --]
next prev parent reply other threads:[~2019-12-10 6:32 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20191203142243.9552.27513@vcs0.savannah.gnu.org>
[not found] ` <20191203142246.0615C20A2B@vcs0.savannah.gnu.org>
2019-12-03 15:08 ` master a6b5985: Avoid duplicated character classes in rx Juanma Barranquero
2019-12-03 15:26 ` Stefan Monnier
2019-12-03 15:33 ` Mattias Engdegård
2019-12-03 16:01 ` Stefan Monnier
2019-12-03 16:06 ` Juanma Barranquero
2019-12-03 17:37 ` Eli Zaretskii
2019-12-03 17:46 ` Juanma Barranquero
2019-12-03 18:34 ` Stefan Monnier
2019-12-03 18:12 ` Drew Adams
2019-12-03 17:39 ` Stefan Monnier
2019-12-03 17:51 ` Juanma Barranquero
2019-12-03 18:36 ` Stefan Monnier
2019-12-03 18:43 ` Juanma Barranquero
2019-12-04 4:36 ` Richard Stallman
2019-12-04 5:38 ` Juanma Barranquero
2019-12-03 19:20 ` Michael Welsh Duggan
2019-12-03 20:21 ` Stefan Monnier
2019-12-04 11:22 ` Mattias Engdegård
2019-12-06 18:49 ` Juanma Barranquero
2019-12-06 19:45 ` Drew Adams
2019-12-06 20:11 ` Juanma Barranquero
2019-12-10 3:27 ` Adam Porter
2019-12-10 4:13 ` Stefan Monnier
2019-12-10 4:20 ` Adam Porter
2019-12-10 6:09 ` Juanma Barranquero
2019-12-10 6:32 ` Juanma Barranquero [this message]
2019-12-06 19:46 ` Eli Zaretskii
2019-12-07 4:48 ` Richard Stallman
2019-12-07 5:45 ` Juanma Barranquero
2019-12-07 15:18 ` Drew Adams
2019-12-08 5:13 ` Richard Stallman
2019-12-03 17:39 ` Drew Adams
2019-12-03 15:36 ` Juanma Barranquero
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=CAAeL0ST7BnTWCCRAdbHvnUqY6Kh1HFXuJfzSdsfWzPQqiHZn5A@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=adam@alphapapa.net \
--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 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.