unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: David Thompson <dthompson2@worcester.edu>
Cc: 22271-done@debbugs.gnu.org
Subject: bug#22271: Cannot use u32vector-set! from (srfi srfi-4)
Date: Tue, 12 Jul 2016 00:10:16 +0200	[thread overview]
Message-ID: <87r3az3jxz.fsf@pobox.com> (raw)
In-Reply-To: <87mvssg11d.fsf@izanagi.i-did-not-set--mail-host-address--so-tickle-me> (David Thompson's message of "Tue, 29 Dec 2015 20:47:42 -0500")

On Wed 30 Dec 2015 02:47, David Thompson <dthompson2@worcester.edu> writes:

> Using Guile built from the master branch at commit
> a9c2606451aebc708f75d0cb02a0b1aa84eec904, I am experiencing a strange
> issue when trying to use u32vector-set in the (srfi srfi-4) module.

Pretty sure this is fixed :)  In any case please open a new bug if you
experience problems with the 2.1 prereleases.

Andy





      reply	other threads:[~2016-07-11 22:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-30  1:47 bug#22271: Cannot use u32vector-set! from (srfi srfi-4) David Thompson
2016-07-11 22:10 ` Andy Wingo [this message]

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=87r3az3jxz.fsf@pobox.com \
    --to=wingo@pobox.com \
    --cc=22271-done@debbugs.gnu.org \
    --cc=dthompson2@worcester.edu \
    /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).