From: Thierry Volpiatto <thierry.volpiatto@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: how to access a large datastructure efficiently?
Date: Thu, 04 Mar 2010 11:24:07 +0100 [thread overview]
Message-ID: <87bpf4tmew.fsf@tux.homenetwork> (raw)
In-Reply-To: loom.20100304T091240-380@post.gmane.org
Christian Wittern <cwittern@gmail.com> writes:
> Thierry Volpiatto <thierry.volpiatto <at> gmail.com> writes:
>
>> >> I have a large list of items which I want to access. The items are in
>> >> sequential order, but many are missing in between, like:
>> >>
>> >> (1 8 17 23 25 34 45 47 50) [in reality, there is a value associated
>> >> with this, but I took it out for simplicity]
>>
>> ,----
>> | (defun closest-elm-in-seq (n seq)
>> | (let ((pair (loop with elm = n with last-elm
>> | for i in seq
>> | if (eq i elm) return (list i)
>> | else if (and last-elm (< last-elm elm) (> i elm)) return
> (list last-elm i)
>> | do (setq last-elm i))))
>> | (if (> (length pair) 1)
>> | (if (< (- n (car pair)) (- (cadr pair) n))
>> | (car pair) (cadr pair))
>> | (car pair))))
>> `----
>> For the smallest just return the car...
>>
>
> This seems to do what I need, thanks! Now I have to see how that
> performs on the real data. I was hoping there would be a method
> that did not involve loops, but some kind of binary search. Would it be
> possible to use a hash-table here?
Yes.
Use loop like this:
,----
| ELISP> (setq A (make-hash-table))
| #s(hash-table size 65 test eql rehash-size 1.5 rehash-threshold 0.8 data
| ())
| ELISP> A
| #s(hash-table size 65 test eql rehash-size 1.5 rehash-threshold 0.8 data
| (1 "a" 2 "b" 3 "c"))
|
| ELISP> (puthash 1 "a" A)
| "a"
| ELISP> (puthash 2 "b" A)
| "b"
| ELISP> (puthash 3 "c" A)
| "c"
| ELISP> (loop for k being the hash-keys in A
| collect k)
| (1 2 3)
|
| ELISP> (loop for v being the hash-values in A
| collect v)
| ("a" "b" "c")
|
| ELISP> (loop for v being the hash-values in A using (hash-key k)
| collect (list k v))
| ((1 "a")
| (2 "b")
| (3 "c"))
`----
--
Thierry Volpiatto
Gpg key: http://pgp.mit.edu/
next prev parent reply other threads:[~2010-03-04 10:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-04 1:50 how to access a large datastructure efficiently? Christian Wittern
2010-03-04 6:59 ` Thierry Volpiatto
2010-03-04 7:25 ` Thierry Volpiatto
2010-03-04 8:13 ` Andreas Röhler
2010-03-04 11:00 ` Thierry Volpiatto
2010-03-04 15:49 ` Andreas Röhler
2010-03-04 16:09 ` Thierry Volpiatto
2010-03-04 8:15 ` Christian Wittern
2010-03-04 10:24 ` Thierry Volpiatto [this message]
2010-03-04 15:01 ` Thien-Thi Nguyen
2010-03-04 16:49 ` Andreas Politz
[not found] <mailman.2247.1267667449.14305.help-gnu-emacs@gnu.org>
2010-03-04 10:36 ` Alan Mackenzie
2010-03-04 20:22 ` Pascal J. Bourguignon
2010-03-05 0:29 ` Stefan Monnier
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=87bpf4tmew.fsf@tux.homenetwork \
--to=thierry.volpiatto@gmail.com \
--cc=help-gnu-emacs@gnu.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.
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).