From: "Juanma Barranquero" <lekktu@gmail.com>
To: "David Kastrup" <dak@gnu.org>
Cc: emacs-devel@gnu.org, Miles Bader <miles@gnu.org>
Subject: Re: "simplifications"
Date: Mon, 19 Nov 2007 13:32:24 +0100 [thread overview]
Message-ID: <f7ccd24b0711190432v4b86f97dj71eb287eee5b7d7@mail.gmail.com> (raw)
In-Reply-To: <86sl32zaqy.fsf@lola.quinscape.zz>
On Nov 19, 2007 1:21 PM, David Kastrup <dak@gnu.org> wrote:
> On the other hand,
> as long as it degrades code quality
"Code quality" is an ambiguous metric, unless you define it. I suppose
you're using some variant of the "code quality = efficiency"
equivalence. Obviously I wasn't. That does not mean that I didn't
think of efficiency (I did, or I wouldn't have done measurements of
ring-member's speed). Though I agree that currently (car (cdr x)) is
faster than (cadr x), I still don't see how that will affect much to
clients of ring.el unless they're doing a quite performance-oriented
use of it. OTOH, code is a bit more readable now IMHO.
> I'd prefer people to refrain from
> doing large-scale "cleanups" or "simplifications" of that kind.
That's about a dozen trivial changes in a package with 165 non-empty,
non-comment lines. Perhaps we should previously agree also in the
definition of "large scale".
> Before we are starting a trend here, it would be nice if the
> optimizations making such changes not have an impact on efficiency
> would be in place.
With this, I agree. You see, I was sure we would find some common
ground after all...
Juanma
next prev parent reply other threads:[~2007-11-19 12:32 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-19 10:46 "simplifications" David Kastrup
2007-11-19 10:56 ` "simplifications" Juanma Barranquero
2007-11-19 15:11 ` "simplifications" Stefan Monnier
2007-11-19 15:19 ` "simplifications" David Kastrup
2007-11-19 15:39 ` "simplifications" Juanma Barranquero
2007-11-19 15:44 ` "simplifications" Stefan Monnier
2007-11-19 15:47 ` "simplifications" Juanma Barranquero
2007-11-19 15:58 ` "simplifications" Stefan Monnier
2007-11-19 16:08 ` "simplifications" Juanma Barranquero
2007-11-19 18:46 ` "simplifications" Stefan Monnier
2007-11-19 16:02 ` "simplifications" David Kastrup
2007-11-19 16:05 ` "simplifications" Juanma Barranquero
2007-11-20 3:59 ` "simplifications" Richard Stallman
2007-11-20 15:27 ` "simplifications" Stefan Monnier
2007-11-21 21:37 ` "simplifications" Stephen J. Turnbull
2007-11-21 21:52 ` "simplifications" David Kastrup
2007-11-22 1:34 ` "simplifications" Stephen J. Turnbull
2007-11-19 11:02 ` "simplifications" Juanma Barranquero
2007-11-19 11:33 ` "simplifications" Miles Bader
2007-11-19 11:57 ` "simplifications" David Kastrup
2007-11-19 12:08 ` "simplifications" Juanma Barranquero
2007-11-19 12:21 ` "simplifications" David Kastrup
2007-11-19 12:32 ` Juanma Barranquero [this message]
2007-11-19 12:49 ` "simplifications" David Kastrup
2007-11-19 12:54 ` "simplifications" Juanma Barranquero
2007-11-20 3:59 ` "simplifications" Richard Stallman
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=f7ccd24b0711190432v4b86f97dj71eb287eee5b7d7@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=dak@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=miles@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.