From 40e9e42bc6ea81bd22c187ba6d08954ab3e0a245 Mon Sep 17 00:00:00 2001 From: Thiago Macieira Date: Sun, 3 Sep 2023 12:04:35 -0700 Subject: [PATCH] Doc: remove erroneous statement that signals can't have return types They can (it's just very, very unusual). Fixes: QTBUG-116695 Pick-to: 6.5 6.6 Change-Id: I2b24e1d3cad44897906efffd178178f1542e67f2 Reviewed-by: Giuseppe D'Angelo --- src/corelib/doc/src/objectmodel/signalsandslots.qdoc | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/src/corelib/doc/src/objectmodel/signalsandslots.qdoc b/src/corelib/doc/src/objectmodel/signalsandslots.qdoc index 7e948548cd..77c2e1f824 100644 --- a/src/corelib/doc/src/objectmodel/signalsandslots.qdoc +++ b/src/corelib/doc/src/objectmodel/signalsandslots.qdoc @@ -110,8 +110,7 @@ when the signal is emitted. Signals are automatically generated by the \l moc and must not be - implemented in the \c .cpp file. They can never have return types - (i.e. use \c void). + implemented in the \c .cpp file. A note about arguments: Our experience shows that signals and slots are more reusable if they do not use special types. If