unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Caleb Ristvedt <caleb.ristvedt@cune.org>
To: 36915@debbugs.gnu.org
Subject: bug#36915: make-thread-local-fluid ignores the default value
Date: Sat, 03 Aug 2019 17:46:19 -0500	[thread overview]
Message-ID: <87sgqh98as.fsf@cune.org> (raw)

In Guile 2.2.6 as packaged on Guix System (x86-64), the following
happens:

--------------------------------------
(define some-fluid (make-thread-local-fluid 42))

(display (fluid-ref some-fluid))

=> #f
--------------------------------------

The same problem doesn't happen with non-thread-local fluids. The manual
says pretty clearly "whose initial value is DFLT", so this should be a
bug.

This is especially significant because, if I understand correctly, that
"default" value is the initial value of that fluid in a new thread. So
just using fluid-set! immediately after creating it isn't sufficient to
work around it entirely.

- reepca





             reply	other threads:[~2019-08-03 22:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-03 22:46 Caleb Ristvedt [this message]
2020-01-12 21:27 ` bug#36915: make-thread-local-fluid ignores the default value Andy Wingo

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=87sgqh98as.fsf@cune.org \
    --to=caleb.ristvedt@cune.org \
    --cc=36915@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).