GNU bug report logs - #79009
[PATCH] Improve 'vtable' object handling, cache handling, messages

Previous Next

Package: emacs;

Reported by: Stéphane Marks <shipmints <at> gmail.com>

Date: Sun, 13 Jul 2025 18:08:01 UTC

Severity: normal

Tags: patch

Full log


Message #26 received at 79009 <at> debbugs.gnu.org (full text, mbox):

From: Stéphane Marks <shipmints <at> gmail.com>
To: Visuwesh <visuweshm <at> gmail.com>
Cc: Spencer Baugh <sbaugh <at> janestreet.com>,
 Kristoffer Balintona <krisbalintona <at> gmail.com>,
 Joost Kremers <joostkremers <at> fastmail.fm>, 79009 <at> debbugs.gnu.org,
 Adam Porter <adam <at> alphapapa.net>, Lars Ingebrigtsen <larsi <at> gnus.org>,
 Augusto Stoffel <arstoffel <at> gmail.com>, ijqq <at> protonmail.com
Subject: Re: bug#79009: [PATCH] Improve 'vtable' object handling, cache
 handling, messages, [PATCH] Improve 'vtable' object handling, cache handling,
 messages
Date: Tue, 15 Jul 2025 13:07:10 -0400
[Message part 1 (text/plain, inline)]
On Tue, Jul 15, 2025 at 11:41 AM Visuwesh <visuweshm <at> gmail.com> wrote:

> [செவ்வாய் ஜூலை 15, 2025] Stéphane Marks wrote:
>
> > On Mon, Jul 14, 2025 at 3:54 PM Spencer Baugh <sbaugh <at> janestreet.com>
> wrote:
> >
> >> Stéphane Marks <shipmints <at> gmail.com> writes:
> >> > On Sun, Jul 13, 2025 at 2:16 PM Stéphane Marks <shipmints <at> gmail.com>
> >> wrote:
> >> > I've updated the broader vtable update in the referenced 78843 bug to
> >> check out if interested.
> >> >
> >> > I've removed support for the duplicate-object feature.  After careful
> >> consideration, it was half baked and I think better for vtable
> >> > programmers to handle their own objects.  I will be sure the
> >> documentation stresses to avoid duplicate objects as vtable's design is
> >> > predicated on unique objects (or race conditions ensue among duplicate
> >> object references).
> >>
> >> Thank you, this was going to be my first bit of feedback.
> >>
> >> Folowup question: What is the motivation for adding customizable object
> >> equality?  Could the need for that be avoided by some changes specific
> >> to vtable-update-object?
> >>
> >
> > It's really a policy question and future proofing.  I believe Lars
> > originated this idea and probably has use cases for this in his vtable
> code.
>
> This question came up in emacs-devel once before:
> https://yhetil.org/emacs-devel/CANVbq5kjPpCKwMBSYfHHLMFXAX7vAgy+D=uLAwJoTGQ5cLSjFQ <at> mail.gmail.com


What does the group have to say about Kristoffer's use case?  He's one of
the people that's helped test the larger vtable.el changes and influenced
some new features and some fixes beyond object-equal.
[Message part 2 (text/html, inline)]

This bug report was last modified 20 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.