Skip to content

Convert all right parenthesis in ordered lists to period #5199

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

Merged
merged 1 commit into from
Feb 21, 2025
Merged

Convert all right parenthesis in ordered lists to period #5199

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 4 additions & 5 deletions docs/code-quality/c26488.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,10 +1,9 @@
---
description: "Learn more about: Warning C26488 LIFETIMES_DEREF_NULL_POINTER"
title: Warning C26488
description: "Learn more about: Warning C26488 LIFETIMES_DEREF_NULL_POINTER"
ms.date: 12/14/2018
f1_keywords: ["C26488", "LIFETIMES_DEREF_NULL_POINTER"]
helpviewer_keywords: ["C26488"]
ms.assetid: 2ade0d31-f259-49de-8676-cce6092fabfc
author: kylereedmsft
ms.author: kylereed
---
Expand All @@ -28,9 +27,9 @@ void ex1()

The Lifetime guidelines from the C++ core guidelines outline a contract that code can follow which will enable more thorough static memory leak and dangling pointer detection. The basic ideas behind the guidelines are:

1) Never dereference an invalid (dangling) or known-null pointer
2) Never return (either formal return or out parameter) any pointer from a function.
3) Never pass an invalid (dangling) pointer to any function.
1. Never dereference an invalid (dangling) or known-null pointer.
1. Never return (either formal return or out parameter) any pointer from a function.
1. Never pass an invalid (dangling) pointer to any function.

## See also

Expand Down
9 changes: 4 additions & 5 deletions docs/code-quality/c26489.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,10 +1,9 @@
---
description: "Learn more about: Warning C26489 LIFETIMES_DEREF_INVALID_POINTER"
title: Warning C26489
description: "Learn more about: Warning C26489 LIFETIMES_DEREF_INVALID_POINTER"
ms.date: 12/14/2018
f1_keywords: ["C26489", "LIFETIMES_DEREF_INVALID_POINTER"]
helpviewer_keywords: ["C26489"]
ms.assetid: 15983d4f-f615-42e7-8521-ee094b87d066
author: kylereedmsft
ms.author: kylereed
---
Expand All @@ -30,9 +29,9 @@ int ex1()

The Lifetime guidelines from the C++ core guidelines outline a contract that code can follow which will enable more thorough static memory leak and dangling pointer detection. The basic ideas behind the guidelines are:

1) Never dereference an invalid (dangling) or known-null pointer
2) Never return (either formal return or out parameter) any pointer from a function.
3) Never pass an invalid (dangling) pointer to any function.
1. Never dereference an invalid (dangling) or known-null pointer.
1. Never return (either formal return or out parameter) any pointer from a function.
1. Never pass an invalid (dangling) pointer to any function.

## See also

Expand Down