unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: Nala Ginrut <nalaginrut@gmail.com>
Cc: Xin Wang <dram.wang@gmail.com>, 16890@debbugs.gnu.org
Subject: bug#16890: current-thread need to be re-exported in srfi-18
Date: Thu, 27 Feb 2014 23:07:35 -0500	[thread overview]
Message-ID: <87iorzq3qw.fsf@yeeloong.lan> (raw)
In-Reply-To: <1393557854.8865.6.camel@Renee-desktop.suse> (Nala Ginrut's message of "Fri, 28 Feb 2014 11:24:14 +0800")

Nala Ginrut <nalaginrut@gmail.com> writes:
> You don't have to import current-thread from srfi-18, it's already in
> top-level.

Not for R6RS code.  This is a genuine bug, and I'll push a fix shortly.

     Mark





  reply	other threads:[~2014-02-28  4:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-27  1:14 bug#16890: current-thread need to be re-exported in srfi-18 Xin Wang
2014-02-28  3:24 ` Nala Ginrut
2014-02-28  4:07   ` Mark H Weaver [this message]
2014-02-28  5:50 ` Mark H Weaver

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=87iorzq3qw.fsf@yeeloong.lan \
    --to=mhw@netris.org \
    --cc=16890@debbugs.gnu.org \
    --cc=dram.wang@gmail.com \
    --cc=nalaginrut@gmail.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).