-
Notifications
You must be signed in to change notification settings - Fork 228
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
Make CesiumGltf headers public and fix warnings #1099
Conversation
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.
Looks good, thanks @azrogers. Just one small comment. Please merge in main as well, since there's a conflict right now.
@@ -103,20 +103,23 @@ class CESIUMUTILITY_API SharedAsset : public CesiumUtility::ExtensibleObject { | |||
* useful to assign the data in derived classes. | |||
*/ | |||
SharedAsset& operator=(const SharedAsset& rhs) { | |||
CesiumUtility::ExtensibleObject::operator=(rhs); | |||
if (rhs != this) { |
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.
This doesn't look right, comparing an instance to a pointer. Shouldn't it be:
if (rhs != this) { | |
if (&rhs != this) { |
Same with the move assignment operator below.
Unfortunately I think I'm going to have to scrap this PR and make a new one since we're no longer going with the |
No need to rush this into this release, moving it out. |
Closing in favor of #1133. |
Closes #460. As part of #1004 we stopped marking most of the public headers as
SYSTEM
so that they would be analyzed by clang-tidy, but we skipped overCesiumGltf
as the number of warnings didn't seem worth resolving at the time. I ended up fixing some of those warnings while working on #1085, so I decided to finish the job here.