all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Pip Cet <pipcet@gmail.com>
Cc: 39529@debbugs.gnu.org, federicotedin@gmail.com
Subject: bug#39529: 28.0.50; Metahelp does not contain help text
Date: Wed, 19 Feb 2020 01:00:37 -0800	[thread overview]
Message-ID: <deef21fb-186d-e18b-11b2-9000a7e52452@cs.ucla.edu> (raw)
In-Reply-To: <CAOqdjBdrB=4ypKiiwxgY7=CXVhicmKxe6Gbx0kofB=e-axWjfA@mail.gmail.com>

On 2/18/20 6:34 PM, Pip Cet wrote:
> (defun hash-equal (a b)
>    (let ((ht (make-hash-table :test 'equal)))
>      (puthash a t ht)
>      (gethash b ht)))
> 
> (hash-equal (point-marker) (point-marker))
> (equal (point-marker) (point-marker))

Ah, OK, then I think we're in fundamental agreement about the problem.

However, I don't agree that the Emacs 27-and-earlier approach is tenable, as 
means that (and (equal a b) (gethash a ht) (not (gethash b ht))) can return t, 
and similarly unexpected and undesirable behavior elsewhere - even if there are 
no side effects on hash keys and no cycles in hash key values. For now it should 
suffice if Emacs handles the case where hash keys don't change and don't have 
cycles; we can worry about the fancier problems later (if ever).





      reply	other threads:[~2020-02-19  9:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-09 19:06 bug#39529: 28.0.50; Metahelp does not contain help text Federico Tedin
2020-02-09 19:22 ` Eli Zaretskii
2020-02-09 19:34   ` Eli Zaretskii
2020-02-15 23:25     ` Paul Eggert
2020-02-16 15:35       ` Eli Zaretskii
2020-02-16 16:51       ` Pip Cet
2020-02-16 19:43         ` Paul Eggert
2020-02-18 19:56           ` Pip Cet
2020-02-19  1:21             ` Paul Eggert
2020-02-19  2:34               ` Pip Cet
2020-02-19  9:00                 ` Paul Eggert [this message]

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=deef21fb-186d-e18b-11b2-9000a7e52452@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=39529@debbugs.gnu.org \
    --cc=federicotedin@gmail.com \
    --cc=pipcet@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 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.