isocpp / isocpp/CppCoreGuidelines
I.22 odd note
Open
@hsutter is already working on this.
Since Jul 9, 2018.
- Dominant language
- CSS
- Stars
- 45.3k
- Forks
- 5.6k
- PR merge metrics
- No merged PRs in 30d
Description
Order of initialization problems become particularly difficult to handle in concurrent code. It is usually best to avoid global (namespace scope) objects altogether.
What does order of initialisation of globals have to do with multithreaded code? (I hope nobody is creating global threads ...)
BTW, singletons with lazy initialisation were a sollution to the initialisation order issue, isn't it?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.