From: Mark Oteiza <mvoteiza@udel.edu>
To: Paul Pogonyshev <pogonyshev@gmail.com>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: (unknown)
Date: Sun, 19 Mar 2017 15:16:49 -0400 [thread overview]
Message-ID: <87k27ljcv2.fsf@holos> (raw)
In-Reply-To: <CAG7BpaozAyUN8Nhp54gOUP=YODUS4Ks+9+tiGqQcCgG=Ym70GQ@mail.gmail.com> (Paul Pogonyshev's message of "Sun, 19 Mar 2017 17:48:13 +0100")
Paul Pogonyshev <pogonyshev@gmail.com> writes:
>>>> Have you tried to measure the impact of your patch on the actual problem?
>>> I mentioned 3%.
>>
>>That's the percentage impact on the number of lambdas. I'm curious
>>about its impact on actual problematic aspects, such as speed and code
>>size (and compilation time, I guess).
>>
>>> Yes, it is practically negligible, but this is a first small patch and
>>> I'm willing to work on improving generators further.
>>
>>Of course.
>
> Actually, forget it. It's too complicated to jump through all the hoops here.
Darn. Such improvements would be nice.
> I would just be glad if someone applied the patch from bug 26068. It's a
> fix, not an optimization, and there is example of a form, evaluation of
> which it fixes.
Applied, thanks. AFAICT it didn't break any tests and didn't exacerbate
bug#12119 which the previous code was fixing.
next prev parent reply other threads:[~2017-03-19 19:16 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-19 16:48 (unknown) Paul Pogonyshev
2017-03-19 19:16 ` Mark Oteiza [this message]
2017-03-19 19:36 ` (unknown) Paul Pogonyshev
-- strict thread matches above, loose matches on Subject: below --
2024-03-13 12:48 (unknown) Eli Zaretskii
2023-11-18 3:13 (unknown) Greg Minshall
2023-11-18 7:05 ` (unknown) Jim Porter
2023-03-13 6:32 (unknown) Pedro Andres Aranda Gutierrez
2023-03-13 6:18 (unknown) Pedro Andres Aranda Gutierrez
2022-10-03 6:30 (unknown) Pedro Andres Aranda Gutierrez
2022-07-21 11:36 (unknown) Gregory Heytings
2022-05-29 6:06 (unknown) Pedro Andres Aranda Gutierrez
2021-12-20 2:29 (unknown) Davin Pearson
2021-08-23 18:37 (unknown) telegraph
2021-08-23 18:36 (unknown) telegraph
2021-07-27 23:54 (unknown) Troy Hinckley
2020-09-06 7:04 (unknown) Ag Ibragimov
2018-04-09 23:58 (unknown) siraben
2017-08-30 19:33 (unknown) Mark Oteiza
2016-12-28 7:15 (unknown) Chris Gregory
2016-12-28 8:58 ` (unknown) Andreas Schwab
2016-09-28 12:26 (unknown) Takesi Ayanokoji
2016-09-29 13:52 ` (unknown) Byung-Hee HWANG (황병희, 黃炳熙)
2016-02-20 15:28 (unknown) Anders Lindgren
2016-02-08 7:54 (unknown) steve
2016-02-08 8:01 ` (unknown) Steve Purcell
2015-08-10 13:59 (unknown) David Kastrup
2015-08-10 14:02 ` (unknown) David Kastrup
2014-11-13 15:21 (unknown) Eli Zaretskii
2014-11-13 15:30 ` (unknown) Lars Magne Ingebrigtsen
2013-07-04 7:50 (unknown) João Távora
2013-07-06 15:22 ` (unknown) Lars Ingebrigtsen
2013-07-06 17:58 ` (unknown) João Távora
2013-07-06 18:01 ` (unknown) Lars Ingebrigtsen
2012-06-29 13:20 (unknown) 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=87k27ljcv2.fsf@holos \
--to=mvoteiza@udel.edu \
--cc=emacs-devel@gnu.org \
--cc=pogonyshev@gmail.com \
/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).