clang-3.7 warns that these std::move calls prevent the copy-elision
optimization that is permitted for returns of named values. Now that
these pointers are always std::unique_ptr, we have no need of the
std::move anyway.
I missed these in an earlier patch, through not building the test
binaries when I checked clang-3.7.
Change-Id: I7b7518564a02c98117c7c7e92dcc7f8d12b7a245
setCorrespondingOutputEntry(entry.get());
entry->setValue(value());
entry->isTextBlock_ = isTextBlock_;
- return move(entry);
+ return entry;
}
void setValue(const std::string &value)
ReferenceDataEntry::EntryPointer entry(
new ReferenceDataEntry(fromXmlString(element->name),
id.toString().c_str()));
- return move(entry);
+ return entry;
}
void readChildEntries(xmlNodePtr parentElement, ReferenceDataEntry *entry)
ReferenceDataEntry::EntryPointer rootEntry(ReferenceDataEntry::createRoot());
readEntry(rootNode, rootEntry.get());
- return move(rootEntry);
+ return rootEntry;
}
//! \endcond
{
ReferenceDataEntry::EntryPointer entry(new ReferenceDataEntry(type, id));
checker.fillEntry(entry.get());
- return move(entry);
+ return entry;
}
//! Checks an entry for correct type and using \p checker.
::testing::AssertionResult