Skip to content

[clang][analyzer][NFC] Fix typos in comments #126676

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 11, 2025
+4 −4
Merged

[clang][analyzer][NFC] Fix typos in comments #126676

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
8 changes: 4 additions & 4 deletions clang/include/clang/StaticAnalyzer/Core/PathSensitive/CallDescription.h
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -35,7 +35,7 @@ class CallDescription {
/// Match calls to functions from the C standard library. This also
/// recognizes builtin variants whose name is derived by adding
/// "__builtin", "__inline" or similar prefixes or suffixes; but only
/// matches functions than are externally visible and are declared either
/// matches functions that are externally visible and are declared either
/// directly within a TU or in the namespace 'std'.
/// For the exact heuristics, see CheckerContext::isCLibraryFunction().
CLibrary,
Expand Down Expand Up @@ -152,7 +152,7 @@ class CallDescription {
/// exists only when that is not available, for example, when _only_
/// syntactic check is done on a piece of code.
///
/// Also, StdLibraryFunctionsChecker::Signature is likely a better candicade
/// Also, StdLibraryFunctionsChecker::Signature is likely a better candidate
/// for syntactic only matching if you are writing a new checker. This is
/// handy if a CallDescriptionMap is already there.
///
Expand Down Expand Up @@ -233,7 +233,7 @@ template <typename T> class CallDescriptionMap {
/// exists only when that is not available, for example, when _only_
/// syntactic check is done on a piece of code.
///
/// Also, StdLibraryFunctionsChecker::Signature is likely a better candicade
/// Also, StdLibraryFunctionsChecker::Signature is likely a better candidate
/// for syntactic only matching if you are writing a new checker. This is
/// handy if a CallDescriptionMap is already there.
///
Expand Down Expand Up @@ -274,7 +274,7 @@ class CallDescriptionSet {
/// exists only when that is not available, for example, when _only_
/// syntactic check is done on a piece of code.
///
/// Also, StdLibraryFunctionsChecker::Signature is likely a better candicade
/// Also, StdLibraryFunctionsChecker::Signature is likely a better candidate
/// for syntactic only matching if you are writing a new checker. This is
/// handy if a CallDescriptionMap is already there.
///
Expand Down