From: Satoshi Ogasawara <ogasawara@itpl.co.jp>
To: "Daniel Bünzli" <daniel.buenzli@erratique.ch>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] [ANN] PEC ver. 1.1
Date: Thu, 19 Apr 2012 22:31:57 +0900 [thread overview]
Message-ID: <4F9013CD.5040804@itpl.co.jp> (raw)
In-Reply-To: <5EE5A4305AC040AABEE680AFA18E0301@erratique.ch>
(2012/04/19 19:57), Daniel Bünzli wrote:
> Le jeudi, 19 avril 2012 à 12:31, Daniel Bünzli a écrit :
> If P1 occurs then you start walking back from L, but you don't know where P1 is so you have to walk down every branch until you find P1 and then walk back from there up to L to make the update.
> Contrast this with (weak) forward pointers: you just start from P1 and walk *once* up to L.
> Is that correct ?
It's correct. But the performance can be optimized in future I think.
When subscribing a event, we can collect and store information about tree structure.
Present implementation discards these information.
Best Regards,
Ogasawara
next prev parent reply other threads:[~2012-04-19 13:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-17 16:40 Satoshi Ogasawara
2012-04-17 17:52 ` Adrien
2012-04-17 18:50 ` Satoshi Ogasawara
2012-04-17 19:23 ` Daniel Bünzli
2012-04-18 1:59 ` Satoshi Ogasawara
2012-04-18 7:36 ` Daniel Bünzli
2012-04-18 11:44 ` Satoshi Ogasawara
2012-04-18 13:27 ` Daniel Bünzli
2012-04-18 17:39 ` Satoshi Ogasawara
2012-04-18 22:32 ` Daniel Bünzli
2012-04-19 8:59 ` Satoshi Ogasawara
2012-04-19 10:31 ` Daniel Bünzli
2012-04-19 10:57 ` Daniel Bünzli
2012-04-19 13:31 ` Satoshi Ogasawara [this message]
2012-04-19 13:02 ` Satoshi Ogasawara
2012-04-19 14:09 ` Daniel Bünzli
2012-04-20 9:24 ` Satoshi Ogasawara
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=4F9013CD.5040804@itpl.co.jp \
--to=ogasawara@itpl.co.jp \
--cc=caml-list@inria.fr \
--cc=daniel.buenzli@erratique.ch \
/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).