From bac2251b8b2783f023bed8f10cd1b0ce1528ebd7 Mon Sep 17 00:00:00 2001 From: Giuseppe D'Angelo Date: Mon, 25 Mar 2024 18:54:08 +0100 Subject: [PATCH] QTypeInfo: do some doc tidies Change-Id: I9893bca7c7fe872e97718b73c4aa08d95d2f74d3 Reviewed-by: Thiago Macieira --- src/corelib/global/qtypeinfo.qdoc | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/src/corelib/global/qtypeinfo.qdoc b/src/corelib/global/qtypeinfo.qdoc index 78d9d423cd..ac55bff1ad 100644 --- a/src/corelib/global/qtypeinfo.qdoc +++ b/src/corelib/global/qtypeinfo.qdoc @@ -13,13 +13,13 @@ \a Flags can be one of the following: \list - \li \c Q_PRIMITIVE_TYPE specifies that \a Type can be created by - zero-initializing its storage, requires no operation to be properly - destroyed, and for which memcpy()ing creates a valid independent - copy of the object. + \li \c Q_PRIMITIVE_TYPE specifies that \a Type requires no + operation to be performed in order to be properly destroyed, + and that it is possible to use memcpy() in order to create a + valid independent copy of an object. \li \c Q_RELOCATABLE_TYPE specifies that \a Type has a constructor - and/or a destructor but can be moved in memory using \c - memcpy(). + and/or a destructor, but it can still be \e{relocated} in memory + by using \c memcpy(). \li \c Q_MOVABLE_TYPE is the same as \c Q_RELOCATABLE_TYPE. Prefer to use \c Q_RELOCATABLE_TYPE in new code. Note: despite the name, this has nothing to do with move constructors or C++ move semantics.