-
At least `zbus_macros` crate doesn't specify versions of internal deps (need to check all our crates) and we know [that's bad](https://gitlab.freedesktop.org/zeenix/zbus/-/merge_requests/89/diffs?comm…
-
At least `zbus_macros` crate doesn't specify versions of internal deps (need to check all our crates) and we know [that's bad](https://gitlab.freedesktop.org/zeenix/zbus/-/merge_requests/89/diffs?comm…
-
While reading https://crates.io/crates/digitalocean, I notice that the code blocks are not highlighted. In the HTML, I see the code element has class `language-unidentified`, indicating that the highl…
-
When dbus crate starts supporting asynchronous calls, we must support that, especially for client-side.
-
The macros to create a service, currently assume that only one object/interface is served on the network. If one needs to serve multiple objects on the bus, they need to launch threads etc, which is c…
-
Would be great if the readme showed an example with dictionaries. Trying to figure that out now.
-
We don't have 'em yet.
-
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