From 63dfd069b3a957361881c12ccba38c5a23b9a42f Mon Sep 17 00:00:00 2001 From: Mike Kaganski Date: Thu, 22 Aug 2019 15:42:36 +0300 Subject: Mark move ctors/assignments noexcept This should enable using move semantics where possible e.g. in standard containers. According to https://en.cppreference.com/w/cpp/language/move_constructor: To make strong exception guarantee possible, user-defined move constructors should not throw exceptions. For example, std::vector relies on std::move_if_noexcept to choose between move and copy when the elements need to be relocated. Change-Id: I6e1e1cdd5cd430b139ffa2fa7031fb0bb625decb Reviewed-on: https://gerrit.libreoffice.org/77957 Tested-by: Jenkins Reviewed-by: Mike Kaganski --- l10ntools/source/po.cxx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'l10ntools/source') diff --git a/l10ntools/source/po.cxx b/l10ntools/source/po.cxx index 921d752ce6c7..20c728e6338c 100644 --- a/l10ntools/source/po.cxx +++ b/l10ntools/source/po.cxx @@ -322,7 +322,7 @@ PoEntry& PoEntry::operator=(const PoEntry& rPo) return *this; } -PoEntry& PoEntry::operator=(PoEntry&& rPo) +PoEntry& PoEntry::operator=(PoEntry&& rPo) noexcept { m_pGenPo = std::move(rPo.m_pGenPo); m_bIsInitialized = std::move(rPo.m_bIsInitialized); -- cgit