Closed KitsuneRal closed 1 month ago
Issues
0 New issues
0 Accepted issues
Measures
0 Security Hotspots
72.2% Coverage on New Code
0.0% Duplication on New Code
@TobiasFella what do you think of switching to const PendingEventItem&
or a Q_GADGET
as a return value for all post*()
calls, eventually or even for 0.9?
@TobiasFella what do you think of switching to
const PendingEventItem&
or aQ_GADGET
as a return value for allpost*()
calls, eventually or even for 0.9?
should be fine for us
looks reasonable, will test later
PendingEventItem
screams that it has semantics of a future even with its name - now one can obtain a future from it and do useful things inthen()
, instead of connecting topendingEvent*
signals. The downside - the future carries no information about the pending item index so it seems of limited use in event item models.