shiboken6: Fix handling of parameters for values with copy constructors only

Introduce a check function to ShibokenGenerator to ensure it is
pass-by-value or pass-by-const-ref to prevent dereferencing the
parameters in case they are passed by pointer (see
QHelpContentItem::childPosition(QHelpContentItem *)).

Change-Id: I385e2bd5c0dfc34ce1ba75cb0c6eebde7ea9c68a
Reviewed-by: Cristian Maureira-Fredes <cristian.maureira-fredes@qt.io>

1 files changed, 6 insertions, 0 deletions

diff --git a/sources/shiboken6/generator/shiboken/shibokengenerator.h b/sources/shiboken6/generator/shiboken/shibokengenerator.h
index aaf88ec53..bcba349cf 100644
--- a/sources/shiboken6/generator/shiboken/shibokengenerator.h
+++ b/sources/shiboken6/generator/shiboken/shibokengenerator.h
@@ -220,10 +220,16 @@ protected:
     static bool isPyInt(const TypeEntry *type);
     static bool isPyInt(const AbstractMetaType &type);
 
+    /// Returns whether the underlying type is a value type with copy constructor only
     static bool isValueTypeWithCopyConstructorOnly(const ApiExtractorResult &api,
                                                    const TypeEntry *type);
     static bool isValueTypeWithCopyConstructorOnly(const ApiExtractorResult &api,
                                                    const AbstractMetaType &type);
+    /// Returns whether the type (function argument) is a value type with
+    /// copy constructor only is passed as value or const-ref and thus
+    /// no default value can be constructed.
+    static bool valueTypeWithCopyConstructorOnlyPassed(const ApiExtractorResult &api,
+                                                       const AbstractMetaType &type);
 
     static bool isNullPtr(const QString &value);