GeoModelShape - Use GeoIntrusivePtr, inline clean ups
- Use GeoIntrusivePtr for GeoShapeUnion, GeoShapeShift, etc.
- Change
const double&
todouble
signature - change mutable double fVolume to std::atomic fVolume.
Merge request reports
Activity
Given these are rather critical changes, can we perhaps make sure that we cleanly break down these changes into individual commits? For example, the comment for 5829c0da says "Use GeoIntrusivePtr" but the commit does way more than this: formatting changes, proper initialization of data members, making various constructor overloads as
delete
, etc. These are all good changes, but I think they should be implemented either in separate commits, or in separate MR-s.Personally, I would avoid trying to make this migration in one giant MR but rather do it in stages, if possible.
Thanks.
added 8 commits
-
f27681f1...818df80e - 5 commits from branch
main
- 2b021b79 - Use GeoIntrusivePtr
- d42c7546 - Include RCBase
- 2c3e7ee1 - More stuff to update
Toggle commit list-
f27681f1...818df80e - 5 commits from branch
added 21 commits
-
28189ac1...3a7e347c - 20 commits from branch
main
- f5c312b9 - Merge branch 'main' into 'GeoSmartLinkUse'
-
28189ac1...3a7e347c - 20 commits from branch
added 6 commits
-
f5c312b9...661778e1 - 5 commits from branch
main
- 880ddb09 - GeoShape - Use Intrusive ptr. Clean up inline
-
f5c312b9...661778e1 - 5 commits from branch
Looks good to me. Tested by building
GeoModelATLAS
on top of it and running somegmcat
tests.See #99 for the discussion about the issues with mac pipelines
mentioned in commit 6011e5b7