[Issue 6114] immutable class variable not properly initialized when the constructor initializing it is non-shared

[via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=6114

--- Comment #8 from Jonathan M Davis  ---
(In reply to Steven Schveighoffer from comment #6)
> The example isn't exactly pointing out the error.
> 
> There are 2 problems here, one is an expectation that a non-shared static
> ctor might run before the shared one (it doesn't, the order is clearly
> defined). That's not really a bug.
> 
> The second is that immutable (shared) data is changing from one thread to
> the next.

Really. what this shows is a side effect of the fact that it's currently
possible to instantiate an object that's treated as shared in a non-shared,
static constructor. It's the fact that the compiler let's you initialize
non-local immutable variables in a non-shared, static constructor that's the
bug. And once that's fixed, this problem goes away.

> I think this should be closed as a dup of 4923.

They're different symptoms of the same bug. So, I have no problem with that.

--

[Issue 6114] immutable class variable not properly initialized when the constructor initializing it is non-shared

[via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=6114

--- Comment #7 from Vladimir Panteleev  ---
Thanks!

--

[Issue 6114] immutable class variable not properly initialized when the constructor initializing it is non-shared

[via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=6114

Steven Schveighoffer  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #6 from Steven Schveighoffer  ---
The example isn't exactly pointing out the error.

There are 2 problems here, one is an expectation that a non-shared static ctor
might run before the shared one (it doesn't, the order is clearly defined).
That's not really a bug.

The second is that immutable (shared) data is changing from one thread to the
next.

I think this should be closed as a dup of 4923.

*** This issue has been marked as a duplicate of issue 4923 ***

--

[Issue 6114] immutable class variable not properly initialized when the constructor initializing it is non-shared

[via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=6114

--- Comment #5 from Jonathan M Davis  ---
Okay, self-contained example:

bug.d

class C
{
}

immutable C theC;

static this()
{
theC = new immutable C;
}


test.d

import bug;

shared static this()
{
assert(theC !is null);
}

void main()
{
}


The assertion fails, but if you make the static constructor in bug.d shared,
then it doesn't.

--

[Issue 6114] immutable class variable not properly initialized when the constructor initializing it is non-shared

[via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=6114

--- Comment #4 from Jonathan M Davis  ---
Really, the larger issue is this one bug# 4923, and maybe this should be closed
given that this is really just another manifestation of that, though if I can
fix the example for this so that it's self-contained, it's a different sort of
example for why immutable globals need to be initialized in shared, static
constructors rather than thread-local ones.

--

[Issue 6114] immutable class variable not properly initialized when the constructor initializing it is non-shared

[via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=6114

--- Comment #3 from Vladimir Panteleev  ---
Jonathan, if this is still an issue, could you please post a complete
self-contained minimal example?

--

[Issue 6114] immutable class variable not properly initialized when the constructor initializing it is non-shared

[via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=6114

Andrei Alexandrescu and...@erdani.com changed:

   What|Removed |Added

Version|unspecified |D2

--

[Issue 6114] immutable class variable not properly initialized when the constructor initializing it is non-shared

[d-bugmail]

http://d.puremagic.com/issues/show_bug.cgi?id=6114


Steven Schveighoffer schvei...@yahoo.com changed:

   What|Removed |Added

 CC||schvei...@yahoo.com


--- Comment #2 from Steven Schveighoffer schvei...@yahoo.com 2011-06-08 
10:41:02 PDT ---
I agree with Jonathan, immutables should not be assignable in non-shared ctors.

The runtime works like this:

1. program startup
2. run all shared static ctors
3. run all thread-local static ctors
4. run application
   4a. on thread creation, run all thread-local static ctors
   4b. on thread destruction, run all thread-local static dtors
5. run all thread-local static dtors
6. run all shared static dtors.
7. end program

So everything is unraveled the same way it was, um... raveled :)

I think since immutable means 'store globally', it should be only assignable
from a shared ctor.  Otherwise, you run into issues.

-- 
Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email
--- You are receiving this mail because: ---

[Issue 6114] immutable class variable not properly initialized when the constructor initializing it is non-shared

[d-bugmail]

http://d.puremagic.com/issues/show_bug.cgi?id=6114


Brad Roberts bra...@puremagic.com changed:

   What|Removed |Added

 CC||bra...@puremagic.com


--- Comment #1 from Brad Roberts bra...@puremagic.com 2011-06-06 00:21:37 PDT 
---
While you've framed this as related to immutable (and I agree with your
assessment), there's a broader problem of the definition of order of
initialization.  For the main thread, is it one or two passes?

-- 
Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email
--- You are receiving this mail because: ---