From: Dustin Sallings <dustin@spy.net>
To: Caml Mailing List <caml-list@inria.fr>
Subject: [Caml-list] removing an item from a list efficiently
Date: Fri, 7 Nov 2003 01:32:19 -0800 [thread overview]
Message-ID: <483F0AC5-1105-11D8-AC71-000393CFE6B8@spy.net> (raw)
I'm trying to implement an LRU cache and I'm using a list to keep up
with the accesses. I'm using filter to remove the item for
repositioning it. That's very slow.
Is there a better way to efficiently move a list item to the front, or
should I just implement a linked list to meet my requirements?
--
Dustin Sallings
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next reply other threads:[~2003-11-07 9:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-07 9:32 Dustin Sallings [this message]
2003-11-07 9:49 ` jrouquie
2003-11-07 12:46 ` Stefano Zacchiroli
2003-11-08 8:49 ` Dustin Sallings
2003-11-08 9:16 ` Stefano Zacchiroli
2003-11-09 1:13 ` Dustin Sallings
2003-11-08 10:59 ` Oleg Trott
2003-11-08 11:02 ` Oleg Trott
2003-11-08 18:57 ` Brian Hurt
2003-11-07 16:50 ` Brian Hurt
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=483F0AC5-1105-11D8-AC71-000393CFE6B8@spy.net \
--to=dustin@spy.net \
--cc=caml-list@inria.fr \
/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 NNTP newsgroup(s).