unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Juanma Barranquero" <lekktu@gmail.com>
To: "Stefan Monnier" <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: "simplifications"
Date: Mon, 19 Nov 2007 16:39:33 +0100	[thread overview]
Message-ID: <f7ccd24b0711190739k20ae35c5ud4feb7604a039158@mail.gmail.com> (raw)
In-Reply-To: <jwv63zyz37s.fsf-monnier+emacs@gnu.org>

On Nov 19, 2007 4:11 PM, Stefan Monnier <monnier@iro.umontreal.ca> wrote:

> 1 - if you use defsubst* the byte-code will look good.

Nice. Thanks!

> 2 - you can use defstruct to get all that and more.

Yes. It's not my code; it it were, I would be using defstruct. I'm a
big Common Lisp fan.

> 3 - I don't think it's worth the trouble to make the byte-optimizer more
>     complex for such little benefit.  If you want to improve it, use the
>     lexbind branch: it's a much saner starting point.

Isn't that branch supposed to be merged back someday?

> it doesn't account for the case where
> you do
> (defsubst cadr (debug-on-error) (car (cdr debug-on-error)))
> in which case the optimization is not semantics preserving"

And I'n not sure it should... I think I agree with David here: if
you're using defsubst to optimize, you should expect some gotchas.

             Juanma

  parent reply	other threads:[~2007-11-19 15:39 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     ` Juanma Barranquero [this message]
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         ` "simplifications" Juanma Barranquero
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

  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=f7ccd24b0711190739k20ae35c5ud4feb7604a039158@mail.gmail.com \
    --to=lekktu@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).