emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debbugs-tracker] bug#27057: closed (26.0.50; Equal defstruct objects no


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#27057: closed (26.0.50; Equal defstruct objects not recognized in puthash)
Date: Wed, 24 May 2017 15:57:02 +0000

Your message dated Wed, 24 May 2017 11:56:25 -0400
with message-id <address@hidden>
and subject line Re: bug#27057: 26.0.50; Equal defstruct objects not recognized 
in puthash
has caused the debbugs.gnu.org bug report #26639,
regarding 26.0.50; Equal defstruct objects not recognized in puthash
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
26639: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=26639
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: 26.0.50; Equal defstruct objects not recognized in puthash Date: Wed, 24 May 2017 11:39:56 -0400
Package: Emacs
Version: 26.0.50

It looks like the new records-based code introduced a bug in the way
records are handled as keys in hash-tables when the test is `equal`:

    (progn
      (cl-defstruct sm-foo a b)
      (setq sm-hash (make-hash-table :test 'equal))
      (puthash (make-sm-foo :a 4 :b 6) "test1" sm-hash)
      (puthash (make-sm-foo :a 4 :b 6) "test2" sm-hash)
      (hash-table-count sm-hash))

this code return 2 here instead of 1.  Lars, could you take a look at it?


        Stefan



--- End Message ---
--- Begin Message --- Subject: Re: bug#27057: 26.0.50; Equal defstruct objects not recognized in puthash Date: Wed, 24 May 2017 11:56:25 -0400 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/26.0.50 (gnu/linux)
>     (progn
>       (cl-defstruct sm-foo a b)
>       (setq sm-hash (make-hash-table :test 'equal))
>       (puthash (make-sm-foo :a 4 :b 6) "test1" sm-hash)
>       (puthash (make-sm-foo :a 4 :b 6) "test2" sm-hash)
>       (hash-table-count sm-hash))
>
> this code return 2 here instead of 1.

This should be fixed now,


        Stefan


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]