-
This is a slightly different issue than #628 - we _record_ the failure internally, it won't be lost, we just don't display it anywhere but in the logs. So it seems from the outside as if the build was…
-
D-Bus supports multiple out parameters so macros should support that too.
-
Just like properties, we should also provide easy way to declare, emit and receive D-Bus signals, just like in Vala: https://wiki.gnome.org/Projects/Vala/Tutorial#Signals
-
In GitLab by @elmarco on Jun 17, 2020, 15:27
Since we're going for the macros as our recommended API, it makes sense to re-export the `zbus_derive` macros in zbus for convenience. It should still be …
-
Since (unlike `zvariant_derive`) this crate's main API are not derive macros, `_derive` in the name is a bit misleading. Best name it `zbus_macros` (or something more appropriate/conventional) before …
-
In GitLab by @elmarco on Jun 17, 2020, 15:27
Since we're going for the macros as our recommended API, it makes sense to re-export the `zbus_derive` macros in zbus for convenience. It should still be …
-
In GitLab by @elmarco on Jun 17, 2020, 15:27
Since we're going for the macros as our recommended API, it makes sense to re-export the `zbus_derive` macros in zbus for convenience. It should still be …
-
Since (unlike `zvariant_derive`) this crate's main API are not derive macros, `_derive` in the name is a bit misleading. Best name it `zbus_macros` (or something more appropriate/conventional) before …
-
Since (unlike `zvariant_derive`) this crate's main API are not derive macros, `_derive` in the name is a bit misleading. Best name it `zbus_macros` (or something more appropriate/conventional) before …
-
Macros aren't very useful if we don't support D-Bus properties, some APIs are very props-based.