Tait Hoyem
Tait Hoyem
Ah yes, it could be any "string" contained in the `kind` field. To deserialize events properly, we sometimes use substitution here, for example with `State`, but I'd also like to...
Revisiting this, since I've been looking for performance uplifts.... Should we do what `zbus` does and have `T` types for events and such properties? I'm unsure if this always makes...
https://gitlab.gnome.org/GNOME/at-spi2-core/-/issues/102
I understand this is meant as a dev-dep. The tests in my case need to be able to be run on the target machine, not just on any machine.
> So you'd compile for the target, which doesn't have a Rust std environment, set the environment variables during compilation, copy the resulting binaries over, and then run the test?...
Looks like the clippy lint is failing on your `main`. Not sure exactly when this is from, but this is not due to a change in my PR.
> but we just use tracing-subscriber and env_logger as they are (i.e., with std enabled unconditionally). How is that going to satisfy your workflow? [`tracing_subscriber` has an `std` feature](https://github.com/tokio-rs/tracing/blob/master/tracing-subscriber/Cargo.toml#L29) that...
> The member name discrepancy has been fixed in zero-copy-zb5, main was not affected / was right. Yes. Thanks for clarifying. > To make us less vulnerable against these kinds...
Cleaned up about 3 dozen. What do you think?
Why do we want this exactly?