llvm-project
[analyzer][NFC] Explain why operator new/delete should never be eval-called
#161370
Merged
Go
Login via GitHub
Home
Pricing
FAQ
Install
Login
via GitHub
Overview
Commits
3
Changes
View On
GitHub
[analyzer][NFC] Explain why operator new/delete should never be eval-called
#161370
balazs-benics-sonarsource
merged 3 commits into
llvm:main
from
balazs-benics-sonarsource:bb/explain-why-operator-new-shouldnt-be-eval-called
[analyzer][NFC] Explain why operator new/delete should never be eval-…
2d0a111e
balazs-benics-sonarsource
requested a review
from
Xazax-hun
3 days ago
balazs-benics-sonarsource
requested a review
from
haoNoQ
3 days ago
balazs-benics-sonarsource
requested a review
from
NagyDonat
3 days ago
balazs-benics-sonarsource
added
clang:static analyzer
llvmbot
added
clang
balazs-benics-sonarsource
requested a review
from
necto
3 days ago
necto
approved these changes on 2025-09-30
balazs-benics-sonarsource
commented on 2025-09-30
balazs-benics-sonarsource
commented on 2025-09-30
Mention PreCall/PostCall as an alternative.
57a083cd
NagyDonat
commented on 2025-09-30
Add the missing `avoid` in comment
251e55d7
NagyDonat
approved these changes on 2025-09-30
balazs-benics-sonarsource
enabled auto-merge (squash)
3 days ago
balazs-benics-sonarsource
merged
afe73f4d
into main
3 days ago
balazs-benics-sonarsource
deleted the bb/explain-why-operator-new-shouldnt-be-eval-called branch
3 days ago
Login to write a write a comment.
Login via GitHub
Reviewers
NagyDonat
necto
Xazax-hun
haoNoQ
Assignees
No one assigned
Labels
clang
clang:static analyzer
Milestone
No milestone
Login to write a write a comment.
Login via GitHub