whytofly
/
qt6-bb10
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

QTypeInfo: do some doc tidies 

Change-Id: I9893bca7c7fe872e97718b73c4aa08d95d2f74d3
Reviewed-by: Thiago Macieira <thiago.macieira@intel.com>
bb10
Giuseppe D'Angelo 2024-03-25 18:54:08 +01:00
parent 3ac259f4cc
commit bac2251b8b
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
src/corelib/global/qtypeinfo.qdoc
View File

@ -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.