From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: Andy Wingo <wingo@pobox.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: subbytevectors
Date: Sat, 09 Jun 2012 17:16:02 +0200 [thread overview]
Message-ID: <87obosbjnx.fsf@gnuvola.org> (raw)
In-Reply-To: <878vfwg2vw.fsf@pobox.com> (Andy Wingo's message of "Sat, 09 Jun 2012 13:07:15 +0200")
() Andy Wingo <wingo@pobox.com>
() Sat, 09 Jun 2012 13:07:15 +0200
Again, the gain in expressiveness is probably worth it
Overall, i am concerned about quick fixes and slow suffering
in the Guile design. To break it down from different angles:
Thinking positively:
If you want to make a case for such a facility, why not
show some code, both without (status quo) and with (proposed)?
It should be clear what expressiveness is gained, and how.
Thinking negatively:
Guile 1.4.x has ‘make-shared-substring’, which is similar in
spirit (since strings of that era are basically byte vectors),
but i believe later Guile versions dropped that. It might be
instructive to (reconstruct if necessary and) follow that chain
of reasoning to avoid repeating a similar flip-flop.
Thinking abstractly:
IIRC, SRFI 13 suggests that its support for substrings would
not be necessary if programmers wrote code using "range" style.
Could the client code you have in mind be rephrased like that?
next prev parent reply other threads:[~2012-06-09 15:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-09 11:07 subbytevectors Andy Wingo
2012-06-09 15:16 ` Thien-Thi Nguyen [this message]
2012-06-09 17:07 ` subbytevectors Andy Wingo
2012-06-11 11:55 ` subbytevectors Ludovic Courtès
2012-06-11 14:01 ` subbytevectors Andy Wingo
2012-06-11 15:35 ` subbytevectors 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=87obosbjnx.fsf@gnuvola.org \
--to=ttn@gnuvola.org \
--cc=guile-devel@gnu.org \
--cc=wingo@pobox.com \
/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).