mgallien added inline comments. INLINE COMMENTS
> anthonyfieroni wrote in extractor.cpp:34 > d *should* never be nullptr If the Extractor is built using the move constructor, the other instance will have a null d pointer. As far as I know, this is standard practice. REPOSITORY R286 KFileMetaData REVISION DETAIL https://phabricator.kde.org/D7750 To: mgallien, #frameworks Cc: dfaure, anthonyfieroni
