You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add define_gv! macro to define named GVariant types, or maybe replace the gv! macro entirely and require GVariant types to be named.
Are my uses of unsafe safe? Could they be avoided?
Is it reasonable to have RefCell in the public API? Would it be better to remove it?
Is it important to implement types (and validation of) object path and type signature types?
Would there be any value in splitting aligned_bytes or casting into their own crates? Or can I replace parts with an existing popular crate?
Set up CI
Fix cargo test attempting to compile my doc comments
Fix CI to run all the relevant tests, fmt and clippy.
Is this suitable to be recommended to be used instead of the GLib implementation in the glib-rs documentation? If not why not and can this be improved accordingly?
The text was updated successfully, but these errors were encountered:
TODO:
gv!
macro to return a type rather than a value?define_gv!
macro to define named GVariant types, or maybe replace thegv!
macro entirely and require GVariant types to be named.RefCell
in the public API? Would it be better to remove it?aligned_bytes
orcasting
into their own crates? Or can I replace parts with an existing popular crate?The text was updated successfully, but these errors were encountered: