From: Daniel Llorens <daniel.llorens@bluewin.ch>
To: 18224-done@debbugs.gnu.org
Subject: bug#18224: bug-guile Digest, Vol 137, Issue 2
Date: Fri, 30 Oct 2015 17:15:21 +0100 [thread overview]
Message-ID: <B58A7E54-7223-4B38-BF27-109295D8DE4A@bluewin.ch> (raw)
In-Reply-To: <mailman.23.1407513605.23914.bug-guile@gnu.org>
http://git.savannah.gnu.org/gitweb/?p=guile.git;a=commitdiff;h=eb3d623da57e6d31a58d95f932345fb761f9b701 on master fixes printing of scm_tc7_array (shared array) to be #1(...) or #1typetag(...) so they aren't confused with actual vectors or bytevectors.
With respect to the lack of capability to create shared bytevectors, use the array procedures instead. If you need the arrays to be contiguous, you can check this at run time.
The fundamental distinction between shared arrays on one side and bytevectors/vectors/bitvectors on the other side is not of contiguity, rank, element type, etc. but that the latter types are containers, while the shared arrays are just views. That is why I don't think indirection fields should be added to the bytevectors, this would complicate the lookup functions and overlap in functionality with arrays.
parent reply other threads:[~2015-10-30 16:15 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <mailman.23.1407513605.23914.bug-guile@gnu.org>]
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=B58A7E54-7223-4B38-BF27-109295D8DE4A@bluewin.ch \
--to=daniel.llorens@bluewin.ch \
--cc=18224-done@debbugs.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).