From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: nnimap blindly assumes that imap server can store arbitrary flags
Date: Mon, 30 May 2011 23:02:54 +0200 [thread overview]
Message-ID: <m38vtnucjl.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <m3r58igtex.fsf@jhcloos.com>
James Cloos <cloos@jhcloos.com> writes:
> (Side note: is it useful to compact a sequence such as (... 55 56 ...)
> into (... (55 . 56) ...)? Is it faster than leaving a sequence of two
> uncompacted?)
They take the same number of cons cells, but the latter allows expanding
to (55 . 57) without generating any garbage or manipulating the
sequence, so it's (marginally) faster in the long run. Possibly.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
next prev parent reply other threads:[~2011-05-30 21:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-26 19:47 James Cloos
2011-05-01 14:54 ` Lars Magne Ingebrigtsen
2011-05-01 15:50 ` Simon Josefsson
2011-05-01 15:56 ` Lars Magne Ingebrigtsen
2011-05-01 18:24 ` James Cloos
2011-05-01 18:30 ` Lars Magne Ingebrigtsen
2011-05-01 18:38 ` James Cloos
2011-05-30 21:11 ` Lars Magne Ingebrigtsen
2011-05-01 18:35 ` James Cloos
2011-05-30 21:02 ` Lars Magne Ingebrigtsen [this message]
2011-05-31 4:52 ` James Cloos
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=m38vtnucjl.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
--cc=ding@gnus.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 NNTP newsgroup(s).