Skip to content

Commit 1c0e97d

Browse files
committed
fix last warnin from bots
1 parent 98d4d95 commit 1c0e97d

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/code-quality/c26840.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ ms.assetid: 2fbe9dc5-fa43-47b9-97a7-3f8215da1d40 # TODO (@carsonradtke): I gener
1414

1515
This warning indicates that the memory was allocated with one family of allocation functions, but was freed with a deallocation function from a different family. This usage is undefined behavior according to the C++ standard and the Microsoft C++ implementation.
1616

17-
The exact ramifications of this defect are difficult to predict. It might result in leaks for classes with destructors that perform memory deallocation. It could cause inconsistent behavior for classes with destructors that perform semantically significant operations, or memory corruptions and crashes. In other cases the mismatch might be unimportant, depending on the implementation of the compiler and its libraries. Analysis tools cannot always distinguish between these situations.
17+
The exact ramifications of this defect are difficult to predict. It might result in leaks for classes with destructors that perform memory deallocation. It could cause inconsistent behavior for classes with destructors that perform semantically significant operations, or memory corruptions and crashes. In other cases the mismatch might be unimportant, depending on the implementation of the compiler and its libraries. Analysis tools can't always distinguish between these situations.
1818

1919
If memory is allocated with one family of allocation functions, it should be freed with a matching deallocation function.
2020

0 commit comments

Comments
 (0)