-
Notifications
You must be signed in to change notification settings - Fork 768
[XPTI] Follow rule of three in XPTI headers #16123
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.
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
Conversation
@@ -734,6 +741,8 @@ class uid_object_t { | |||
MUId.instance = 0; | |||
}; | |||
|
|||
~uid_object_t() = default; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Only has one data member to deal with (xpti::uid128_t MUId
), so default destructor should be fine
tracepoint_t(const tracepoint_t &) = delete; | ||
tracepoint_t &operator=(const tracepoint_t &) = delete; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if a tracepoint_t
object with m_top
set to true is copied we would call xptiSetUniversalId(xpti::invalid_uid)
twice on both of their destructions, so we likely do not want to be able to copy.
@intel/llvm-reviewers-runtime @sergey-semenov Friendly ping |
Failed Tests (1): |
No description provided.