Permalink
ReplySay I have a static context stack in my class Context, will each new thread receive their own copy of the static member or do I have to account for multiple threads and do it myself?
| Thread overview | |||||
|---|---|---|---|---|---|
|
1 day ago How does D lang handle multithreaded applications and static members of classes? | ||||
|---|---|---|---|---|
| ||||
 | ||||
1 day ago Re: How does D lang handle multithreaded applications and static members of classes? | ||||
|---|---|---|---|---|
| ||||
 Posted in reply to Daniel Donnelly, Jr. | On Tuesday, 1 April 2025 at 23:01:23 UTC, Daniel Donnelly, Jr. wrote: >Say I have a static context stack in my class Context, will each new thread receive their own copy of the static member or do I have to account for multiple threads and do it myself? All global variables in D, including static class members, are thread local by default. You have to explicitly add the | |||
1 day ago Re: How does D lang handle multithreaded applications and static members of classes? | ||||
|---|---|---|---|---|
| ||||
Posted in reply to Inkrementator | On Wednesday, 2 April 2025 at 08:33:05 UTC, Inkrementator wrote: >On Tuesday, 1 April 2025 at 23:01:23 UTC, Daniel Donnelly, Jr. wrote: >Say I have a static context stack in my class Context, will each new thread receive their own copy of the static member or do I have to account for multiple threads and do it myself? All global variables in D, including static class members, are thread local by default. You have to explicitly add the Thats a good thing. The default is great for my app. | |||
Copyright © 1999-2021 by the D Language Foundation