From: Arthur Miller <arthur.miller@live.com>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: emacs-devel@gnu.org
Subject: Re: Q: BLV for function slots + BL obarray/hmap for symbol lookup?
Date: Sun, 30 May 2021 04:57:28 +0200 [thread overview]
Message-ID: <AM9PR09MB49776B185ED1DF5F5A75086196209@AM9PR09MB4977.eurprd09.prod.outlook.com> (raw)
In-Reply-To: <87r1hp675v.fsf@web.de> (Michael Heerdegen's message of "Sat, 29 May 2021 14:44:44 +0200")
Michael Heerdegen <michael_heerdegen@web.de> writes:
> Arthur Miller <arthur.miller@live.com> writes:
>
>
>> (setq-local obarray (copy-sequence obarray))
> ^^^^^^^^^^^^^
>
> I guess this is something different than with the originally suggested
> `obarray-copy'.
>
> I once was told that obarray is not just simply an array of existing
> symbols
You mean I got a shallow copy of the obarray instead of a deep copy?
Where do I find this obarray-copy? :-) I don't see it in 27.1.
> (length obarray) ==> 15121
Yes, I get the same apocalytpic number, surprise :).
> (let ((i 0)) (mapatoms (lambda (_) (cl-incf i))) i) ==> 66002
I get 45416.
This is beyond my knowledge about how obarrays in Emacs are made. I just
looked quickly in the source and see that make-obarray is in principle
just a wrapper for (make-vector size 0), which then calls into
make_vector in C code, so obviouslu the vector is allocated elsewhere
since the length is a prime number. I guess it is just the number of
predefined slots in the vector for hashing, not the actually numer of
symbols in the array? I guess just buckets for chaining? I am not sure
how to interpret the second number from mapatoms, collisions? :) But I
am probably wrong, just speculating.
next prev parent reply other threads:[~2021-05-30 2:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-22 21:46 Q: BLV for function slots + BL obarray/hmap for symbol lookup? Arthur Miller
2021-05-22 22:30 ` Stefan Monnier
2021-05-22 23:31 ` Arthur Miller
2021-05-23 3:25 ` Stefan Monnier
2021-05-23 9:00 ` Arthur Miller
2021-05-23 15:27 ` Stefan Monnier
2021-05-23 16:23 ` Arthur Miller
2021-05-29 7:31 ` Arthur Miller
2021-05-29 12:44 ` Michael Heerdegen
2021-05-30 2:57 ` Arthur Miller [this message]
2021-05-30 12:44 ` Philipp
2021-05-29 13:47 ` Stefan Monnier
2021-05-30 2:30 ` Arthur Miller
2021-05-30 2:44 ` Stefan Monnier
2021-05-30 12:17 ` Arthur Miller
2021-05-29 13:56 ` Stefan Monnier
2021-05-23 18:22 ` Clément Pit-Claudel
2021-05-23 20:23 ` Arthur Miller
2021-05-23 21:41 ` Clément Pit-Claudel
2021-05-24 12:37 ` Arthur Miller
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=AM9PR09MB49776B185ED1DF5F5A75086196209@AM9PR09MB4977.eurprd09.prod.outlook.com \
--to=arthur.miller@live.com \
--cc=emacs-devel@gnu.org \
--cc=michael_heerdegen@web.de \
/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).