From: John Mastro <john.b.mastro@gmail.com>
To: emacs-devel <emacs-devel@gnu.org>
Cc: "Michael Heerdegen" <michael_heerdegen@web.de>,
"Clément Pit--Claudel" <clement.pit@gmail.com>
Subject: Re: [PATCH] Elpa: Pinpoint semantics of `seq-subseq' for streams
Date: Wed, 14 Sep 2016 17:51:05 -0700 [thread overview]
Message-ID: <CAOj2CQTH=NVAKoBig8XmjCcqLPDMp6dsDaFo66PdycUfBUG+mQ@mail.gmail.com> (raw)
In-Reply-To: <dc917534-7d46-1998-af9b-25a172a8f4c7@gmail.com>
Clément Pit--Claudel <clement.pit@gmail.com> wrote:
>> I think this is actually a very good example why it is good to
>> forbid negative indexes. If you are interested in the last n lines
>> of a file, why would you dissect the complete file (or buffer) into
>> lines and throw away nearly all of the result?
>
> Because it's much more memory-efficient, as long as the file's lines
> are short :) Note that I was careful to say file, not buffer: I don't
> need to load a full file in memory before I start processing its
> lines. Same for the output of a running process: if I just want the
> last n lines, then accumulating all of the output before going to the
> end and looking backwards is extremely inefficient, memory-wise.
> Dissecting the output (splitting it on newlines) and using a ring
> buffer to keep only the last `n` ones is much better.
(Asking for my own edification)
Wouldn't finding the last N elements require forcing every thunk in the
stream (to find its end), thus using more memory than a linked list with
the same contents? As long as you don't "hang on to the head" of the
stream, earlier elements could be reclaimed by GC, but the same applies
to a list.
In short, I find this conversation interesting, but don't quite
understand where the memory savings come in :)
John
next prev parent reply other threads:[~2016-09-15 0:51 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-13 16:23 [PATCH] Elpa: Pinpoint semantics of `seq-subseq' for streams Michael Heerdegen
2016-09-13 18:02 ` Clément Pit--Claudel
2016-09-13 21:17 ` Michael Heerdegen
2016-09-14 1:24 ` Clément Pit--Claudel
2016-09-14 15:05 ` Michael Heerdegen
2016-09-14 23:26 ` Clément Pit--Claudel
2016-09-15 0:51 ` John Mastro [this message]
2016-09-15 2:00 ` Clément Pit--Claudel
2016-09-15 17:01 ` John Mastro
2016-09-15 21:07 ` Michael Heerdegen
2016-09-15 22:18 ` Clément Pit--Claudel
2016-09-15 22:28 ` Michael Heerdegen
2016-09-15 22:52 ` Clément Pit--Claudel
2016-09-15 0:58 ` Michael Heerdegen
2016-09-15 3:47 ` Clément Pit--Claudel
2016-09-15 8:42 ` Nicolas Petton
2016-09-15 22:30 ` Michael Heerdegen
2016-09-15 23:08 ` Nicolas Petton
2016-09-15 21:29 ` Michael Heerdegen
2016-09-14 1:28 ` John Wiegley
2016-09-14 15:15 ` Michael Heerdegen
2016-09-13 22:20 ` Nicolas Petton
2016-09-13 22:40 ` Michael Heerdegen
2016-09-14 8:25 ` Nicolas Petton
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='CAOj2CQTH=NVAKoBig8XmjCcqLPDMp6dsDaFo66PdycUfBUG+mQ@mail.gmail.com' \
--to=john.b.mastro@gmail.com \
--cc=clement.pit@gmail.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.