Follow-up from "fix(core): concurrent access errors with GDCM when accessing to DICOM data from different threads"
The following discussion from !1074 (merged) should be addressed:
-
@aancel1 started a discussion: I'd suggest opening an issue with the comment in your MR description if not already done:
we may one day try to better encapsulate the methods that really requier gdcm::SmartPointer<> to reduce the critical section. We may also refactor a bit fiducial_series that uses extensively gdcm::SmartPointer<> and even expose it in the header, violating the original pimp design.
So that we keep that in the pipe of things to do