Task/Promise: Don't allow abstract types

Supporting abstract types only has little advantages and we might want
to store the result by value later.

1 files changed, 1 insertions, 8 deletions

diff --git a/src/base/QXmppTask.h b/src/base/QXmppTask.h
index 141cf10e..84ba8a33 100644
--- a/src/base/QXmppTask.h
+++ b/src/base/QXmppTask.h
@@ -50,10 +50,6 @@ private:
 ///
 /// Tasks are generated by QXmppPromise and can be handled using QXmppTask::then().
 ///
-/// It supports abstract types, i.e. you can create a QXmppTask<QXmppStanza> and report MyIq
-/// (derived from QXmppStanza) to it and when handling the result it is possible to cast the result
-/// back to MyIq.
-///
 /// Unlike QFuture, this is not thread-safe. This avoids the need to do mutex locking at every
 /// access though.
 ///
@@ -177,10 +173,7 @@ public:
     ///
     /// Moves the result of the operation out of the task.
     ///
-    /// Since this returns by value, you will not be able to cast the result to derived types. Use
-    /// result() for read-only access or register a handler function using then().
-    ///
-    /// \warning This can only be used once the operation is finished.
+    /// \warning This can only be used once and only after the operation has finished.
     ///
 #ifdef QXMPP_DOC
     [[nodiscard]] T takeResult()