Have const and non-const signatures side by side

To satisfy Neochat that already ended up depending on the new (const) signature.
quotient-im · Sep 11, 2023 · ece707e · ece707e
1 parent 16bde5d
commit ece707e
Show file tree

Hide file tree

Showing 2 changed files with 8 additions and 1 deletion.
diff --git a/Quotient/room.cpp b/Quotient/room.cpp
@@ -1218,6 +1218,11 @@ Room::rev_iter_t Room::fullyReadMarker() const
     return findInTimeline(d->fullyReadUntilEventId);
 }
 
+QSet<QString> Room::userIdsAtEvent(const QString& eventId) const
+{
+    return d->eventIdReadUsers.value(eventId);
+}
+
 QSet<QString> Room::userIdsAtEvent(const QString& eventId)
 {
     return d->eventIdReadUsers.value(eventId);

diff --git a/Quotient/room.h b/Quotient/room.h
@@ -512,7 +512,9 @@ class QUOTIENT_API Room : public QObject {
     //!       it's recommended to ensure that all room members are loaded
     //!       before operating on the result of this function.
     //! \sa lastReadReceipt, allMembersLoaded
-    QSet<QString> userIdsAtEvent(const QString& eventId);
+    QSet<QString> userIdsAtEvent(const QString& eventId) const;
+
+    QSet<QString> userIdsAtEvent(const QString& eventId); // See #706
 
     [[deprecated("Use userIdsAtEvent instead")]]
     QSet<User*> usersAtEventId(const QString& eventId);