unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Spencer Baugh <sbaugh@catern.com>
Cc: sbaugh@catern.com, monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: [PATCH 0/7] Cleanups and tests for DEFVAR_PER_BUFFER variables
Date: Wed, 24 Mar 2021 01:36:17 -0400	[thread overview]
Message-ID: <E1lOwBl-0000ZJ-Eo@fencepost.gnu.org> (raw)
In-Reply-To: <cover.1616554376.git.sbaugh@catern.com> (message from Spencer Baugh on Tue, 23 Mar 2021 23:11:50 -0400)

> From: Spencer Baugh <sbaugh@catern.com>
> Date: Tue, 23 Mar 2021 23:11:50 -0400
> Cc: Spencer Baugh <sbaugh@catern.com>, Eli Zaretskii <eliz@gnu.org>,
>  Stefan Monnier <monnier@iro.umontreal.ca>
> 
> Hi emacs-devel,

Actually, it is best to send this (and patches in general) to
bug-gnu-emacs@gnu.org, so that the whole discussion is recorded by our
issue tracker.

> These are some cleanups and tests for DEFVAR_PER_BUFFER variables.
> I think they are all uncontroversial.
> 
> These are extracted from the patch series I sent some months ago
> (Subject: Speeding up DEFVAR_PER_BUFFER).  Specifically, these are the
> patches that were approved as fine independent of the rest of the
> series.  And they have changelog entries in the commit messages now :)
> 
> These are pre-requisites for my DEFVAR_PER_BUFFER improvements (which
> I'll be resending soon), so it would be nice to apply them ahead of
> that.

I'd prefer to pick up where we left off back then.  The main issue
left unresolved in the past discussion was the potential slowdown of
simple accesses to buffer-local vars due to your proposal.  Can we
please have benchmarks for that, so we could decide whether the
tradeoff is worth it?  It's quite possible that the performance
aspects could affect the code changes, so even uncontroversial
cleanups should perhaps wait until we have figured out the more
important aspects of these changesets.

Thanks.



  parent reply	other threads:[~2021-03-24  5:36 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-24  3:11 [PATCH 0/7] Cleanups and tests for DEFVAR_PER_BUFFER variables Spencer Baugh
2021-03-24  3:11 ` [PATCH 1/7] Add a test for let-binding unwinding Spencer Baugh
2021-03-24  3:11 ` [PATCH 2/7] Assert not local-variable-p after setq in let_default binding Spencer Baugh
2021-03-24  3:11 ` [PATCH 3/7] Stop checking the constant default for enable_multibyte_characters Spencer Baugh
2021-03-24  3:11 ` [PATCH 4/7] Take buffer field name in DEFVAR_PER_BUFFER Spencer Baugh
2021-03-24  3:11 ` [PATCH 5/7] Combine unnecessarily separate loops in buffer.c Spencer Baugh
2021-03-24  3:11 ` [PATCH 6/7] Assert that PER_BUFFER_IDX for Lisp variables is not 0 Spencer Baugh
2021-03-24  3:11 ` [PATCH 7/7] Remove unnecessary Qunbound check Spencer Baugh
2021-03-25 16:46   ` Stefan Monnier
2021-03-24  5:36 ` Eli Zaretskii [this message]
2021-03-25 16:48   ` [PATCH 0/7] Cleanups and tests for DEFVAR_PER_BUFFER variables Stefan Monnier
2021-03-25 17:00     ` Eli Zaretskii
2021-04-01 18:13   ` Spencer Baugh
2021-04-01 18:51     ` Eli Zaretskii
2021-04-03 20:53       ` Spencer Baugh
2021-04-04  7:15         ` Eli Zaretskii
2021-04-01 21:42     ` Stefan Monnier
2021-04-01 23:39       ` Spencer Baugh
2021-04-02  2:55         ` Stefan Monnier
2021-04-02  5:36       ` 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=E1lOwBl-0000ZJ-Eo@fencepost.gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=sbaugh@catern.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).