From: Mikael Djurfeldt <mdj@kvast.blakulla.net>
Cc: djurfeldt@nada.kth.se, guile-devel@gnu.org
Subject: Shared arrays
Date: Thu, 28 Oct 2004 11:31:19 +0200 [thread overview]
Message-ID: <E1CN6cp-00029u-FY@witch> (raw)
2004-10-27 Marius Vollmer <marius.vollmer@uni-dortmund.de>
First cut at integrating uniform vectors from srfi-4 with the rest
of Guile. This change replaces scm_tc7_byvect with a s8 uniform
vector. The plan is to gradually replace one type after the other
until none is left and then to consider general cleanups and
optimizations.
This is great. Just one comment. I do hope we'll keep the ability to
create shared arrays. This is similar in spirit to list structures
and mutation-sharing substrings, and extremely useful.
M
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next reply other threads:[~2004-10-28 9:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-28 9:31 Mikael Djurfeldt [this message]
2004-10-28 11:48 ` Shared arrays Marius Vollmer
2004-10-28 11:54 ` Mikael Djurfeldt
2004-10-28 12:15 ` Marius Vollmer
2004-10-30 14:38 ` Neil Jerram
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=E1CN6cp-00029u-FY@witch \
--to=mdj@kvast.blakulla.net \
--cc=djurfeldt@nada.kth.se \
--cc=guile-devel@gnu.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).