unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: 56255@debbugs.gnu.org
Subject: bug#56255: 28.1.50; sxhash-equal does not change when object is modified
Date: Thu, 30 Jun 2022 11:06:34 +0200	[thread overview]
Message-ID: <871qv6frl1.fsf@gnus.org> (raw)
In-Reply-To: <87czerk4qo.fsf@localhost> (Ihor Radchenko's message of "Wed, 29 Jun 2022 20:56:31 +0800")

Ihor Radchenko <yantar92@gmail.com> writes:

> As for the hash tables and collisions. Are you sure that collisions are
> OK? Consider the following example:
>
> (setq a (avl-tree--create #'org-element--cache-compare))
> (avl-tree-enter a '(headline (:begin 2)))
> (setq tbl (make-hash-table :test #'equal))
> (puthash a 'value tbl)
> (gethash a tbl)
> (plist-put (nth 1 (avl-tree-first a)) :begin 10)
> (gethash a tbl) ;; the value does not change!

That has nothing to do with collisions -- you're free to alter a key as
much as you want.  It's just a normal Lisp object.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2022-06-30  9:06 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
2022-06-29 12:38                 ` Lars Ingebrigtsen
2022-06-29 12:56                   ` Ihor Radchenko
2022-06-30  9:06                     ` Lars Ingebrigtsen [this message]
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

  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=871qv6frl1.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=56255@debbugs.gnu.org \
    --cc=yantar92@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).