From: Andy Wingo <wingo@pobox.com>
To: guile-devel <guile-devel@gnu.org>
Subject: proposal: deprecate dynamic states
Date: Sun, 09 Mar 2014 18:33:56 +0100 [thread overview]
Message-ID: <87eh2b2s57.fsf@pobox.com> (raw)
Hi,
The manual claims that you can use fluids as thread-local variables, but
that's not really true -- we expose this strange "dynamic state"
interface that lets you have one dynamic state used by multiple
threads. Pretty strange stuff.
Normally I wouldn't be against "extra functionality" but this one makes
no sense. We need something that is "thread-local state" and
fluids/parameters should be that thing -- and yet, we are prevented from
doing by the dynamic state interface. (Of course, that doesn't stop us
from using fluids in this way; I'm sure there are many bugs out there.)
So my proposal is to deprecate the dynamic state interface. It's
nonstandard, I've never heard of anyone using it, and it's actively
harmful. If no one objects, I'll push something that does this in the
next couple days.
Andy
--
http://wingolog.org/
next reply other threads:[~2014-03-09 17:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-09 17:33 Andy Wingo [this message]
2014-03-09 21:55 ` proposal: deprecate dynamic states Mark H Weaver
2014-03-10 13:26 ` Ludovic Courtès
2016-06-19 15:36 ` Andy Wingo
-- strict thread matches above, loose matches on Subject: below --
2016-06-26 11:26 Josep Portella Florit
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=87eh2b2s57.fsf@pobox.com \
--to=wingo@pobox.com \
--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).