all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 56255@debbugs.gnu.org
Subject: bug#56255: 28.1.50; sxhash-equal does not change when object is modified
Date: Wed, 29 Jun 2022 20:33:05 +0800	[thread overview]
Message-ID: <87ilojk5tq.fsf@localhost> (raw)
In-Reply-To: <87fsjnlqrh.fsf@gnus.org>

Lars Ingebrigtsen <larsi@gnus.org> writes:

> Ihor Radchenko <yantar92@gmail.com> writes:
>
>> This is exactly the problem at hand. I was hoping to find a fast way to
>> detect if a large deeply nested object is changed. If not, do not print
>> that object for the purpose of saving it to disk cache. Printing can
>> take up to 2-3 seconds in some cases.
>
> I think you basically have to restructure the code to add a guard to
> whatever's updating the structure to see whether it's "dirty" or not.

This is only possible when I have access to the code making changes to
the object.

The original idea was to detect changed objects in most generic way, as
a part of persistent storage library. Oh well.

Best,
Ihor





  reply	other threads:[~2022-06-29 12:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-27 12:27 bug#56255: 28.1.50; sxhash-equal does not change when object is modified Ihor Radchenko
2022-06-27 22:56 ` Lars Ingebrigtsen
2022-06-27 23:00   ` Lars Ingebrigtsen
2022-06-28 12:58     ` Lars Ingebrigtsen
2022-06-29  1:58       ` Ihor Radchenko
2022-06-29 10:01         ` Lars Ingebrigtsen
2022-06-29 10:12           ` Ihor Radchenko
2022-06-29 10:15             ` Lars Ingebrigtsen
2022-06-29 12:33               ` Ihor Radchenko [this message]
2022-06-29 12:38                 ` Lars Ingebrigtsen
2022-06-29 12:56                   ` Ihor Radchenko
2022-06-30  9:06                     ` Lars Ingebrigtsen
2022-06-30 11:16                       ` Ihor Radchenko

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=87ilojk5tq.fsf@localhost \
    --to=yantar92@gmail.com \
    --cc=56255@debbugs.gnu.org \
    --cc=larsi@gnus.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.