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 <mike.kaganski@collabora.com>

1 files changed, 2 insertions, 2 deletions

diff --git a/sd/source/ui/view/OutlinerIterator.cxx b/sd/source/ui/view/OutlinerIterator.cxx
index 63e4288b7009..8546b9f63264 100644
--- a/sd/source/ui/view/OutlinerIterator.cxx
+++ b/sd/source/ui/view/OutlinerIterator.cxx
@@ -65,7 +65,7 @@ Iterator::Iterator (const Iterator& rIterator)
 {
 }
 
-Iterator::Iterator (Iterator&& rIterator)
+Iterator::Iterator(Iterator&& rIterator) noexcept
     : mxIterator(std::move(rIterator.mxIterator))
 {
 }
@@ -91,7 +91,7 @@ Iterator& Iterator::operator= (const Iterator& rIterator)
     return *this;
 }
 
-Iterator& Iterator::operator= (Iterator&& rIterator)
+Iterator& Iterator::operator=(Iterator&& rIterator) noexcept
 {
     mxIterator = std::move(rIterator.mxIterator);
     return *this;