Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Construction order for thread_local objects is unclear #17

Closed
sdutoit opened this issue May 11, 2012 · 2 comments
Closed

Construction order for thread_local objects is unclear #17

sdutoit opened this issue May 11, 2012 · 2 comments
Assignees
@sdutoit

Comments

@sdutoit
Copy link
Contributor

sdutoit commented May 11, 2012

The order (and frequency) of construction is implicit, but the current wording is very terse and deserves at least a note to clarify the intent.

There may also be a CWG issue about when the arguments to such a constructor call are evaluated.
@ghost ghost assigned sdutoit May 11, 2012
@sdutoit
Copy link
Contributor Author

sdutoit commented Apr 15, 2013

Richard Smith pointed out that there are more issues in this area (surprise!).

Specifically, having a thread local inside of a template will require initialization of all thread local storage across all translation units that happen to instantiate that template.

@zygoloid
Copy link
Member

It's not clear that we should to do anything editorially here, nor that this is worth forwarding as a core issue. (For reference, we assume this refers to [basic.start.init]p2.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sdutoit sdutoit

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@zygoloid @sdutoit