Re: proposal: deprecate dynamic states

[Mark H Weaver]

Hi Andy,

Andy Wingo <address@hidden> writes:

> 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.

I strongly agree with this.

> If no one objects, I'll push something that does this in the next
> couple days.

Sounds good to me!

     Mark