You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
- create code fences with backticks ` or tildes ~ ```
like so
``` - add language identifier to highlight code ```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible) <https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. design-patterns), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you
lang-cpp
AandB. If one thread throws, rolling backA'stransaction should not destroy resources allocated inB, e.g. -- the thread states are independent of each other, and persistent memory living on the heap is independent of both. However, typically in C++, heap memory is still tied to objects on the stack.std::vectorobject might live on the stack but point to memory on the heap -- both the vector object (on the stack) and its contents (on the heap) would be deallocated during a stack unwind in that case, since destroying the vector on the stack would invoke a destructor which frees the associated memory on the heap (and likewise destroy those heap elements). Typically for exception-safety, most C++ objects live on the stack, even if they're only handles pointing to memory on the heap, automating the process of freeing both heap and stack memory on stack unwind.