Replymessage unavailable
Well, sadly I cannot recall the exact case with a plain @Slot(), but as mentioned, using it allows you to add them to the QMetaObject at type parsing time, rather than when you connect a signal to it.
(see long discussion here https://bugreports.qt.io/browse/PYSIDE-315 ), also implying hat the instance of the dynamic QMetaObject is the same as the application, there is a detail implementation that when we register the Signal-Slot connections, another instance of the QMetaObject is created.
There seems to also be a requirement for Mixin Signals.
Other perks come from the arguments,
-@Slot(type) for specification on which slot to trigger (useful for QML too)
- Some people rely on having a @Slot(name="something") then connecting a signal to something, and other arguments.
Using the @Slot decorator also helps with solutions like Nuitka ( https://bugreports.qt.io/browse/PYSIDE-1589 )