From: Andy Wingo <wingo@pobox.com>
To: Mark H Weaver <mhw@netris.org>
Cc: "Ludovic Courtès" <ludo@gnu.org>, guile-devel@gnu.org
Subject: Re: O(1) accessors for UTF-8 backed strings
Date: Sat, 19 Mar 2011 14:02:23 +0100 [thread overview]
Message-ID: <m38vwbw9eo.fsf@unquote.localdomain> (raw)
In-Reply-To: <87ipvkmlog.fsf@netris.org> (Mark H. Weaver's message of "Tue, 15 Mar 2011 11:46:07 -0400")
On Tue 15 Mar 2011 16:46, Mark H Weaver <mhw@netris.org> writes:
> I'd also like to point out that the R6RS is the only relevant standard
> that mandates O(1) string accessors. The R5RS did not require this, and
> WG1 for the R7RS has already voted against this requirement.
>
> http://trac.sacrideo.us/wg/ticket/27
Only tangentially related to the question under discussion, but I find
this a bit baffling. I found
http://trac.sacrideo.us/wg/wiki/StringRepresentations, but it's a lot of
original work (record1 ??), and doesn't lead to any conclusions.
http://trac.sacrideo.us/wg/wiki/WG1Ballot1Results lists no rationales.
Grr.
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2011-03-19 13:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-11 0:54 uc_tolower (uc_toupper (x)) Mike Gran
2011-03-11 22:33 ` Using libunistring for string comparisons et al Mark H Weaver
2011-03-11 22:36 ` Mark H Weaver
2011-03-11 23:09 ` Mark H Weaver
2011-03-12 13:46 ` Ludovic Courtès
2011-03-12 17:28 ` Mark H Weaver
2011-03-13 21:30 ` Ludovic Courtès
2011-03-30 9:05 ` Andy Wingo
2011-03-13 4:05 ` O(1) accessors for UTF-8 backed strings Mark H Weaver
2011-03-13 4:42 ` Alex Shinn
2011-03-15 15:46 ` Mark H Weaver
2011-03-16 0:07 ` Alex Shinn
2011-03-19 13:02 ` Andy Wingo [this message]
2011-03-30 9:20 ` Andy Wingo
2011-03-30 9:03 ` Using libunistring for string comparisons et al Andy Wingo
2011-03-31 14:19 ` Ludovic Courtès
2011-03-12 13:36 ` Ludovic Courtès
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m38vwbw9eo.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=mhw@netris.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).