Sebastian Dröge

Use `T: AsRef<str>, &[T]` instead of `&[&str]` in various APIs

5

Much nicer to use if your strings are actual `String`. Same thing applies for other `&[&T]` we might have in API somewhere as with `AsRef` both `&[T]` and `&[&T]` would...

Add lifetime parameter to FromVariant trait for allowing to borrow slices, strings, etc.

1

See summary.

Add convenience futures API

24

Compared to async-std/tokio it's rather verbose and inconvenient to use. Something like the following, inspired by the beforementioned APIs and how gio works. We would then step by step extend...

FromGlibPtr* extension for borrowing

7

It would be good if FromGlibPtr* could get some variant that can be used for borrowing, mutably and immutably. Rationale for this is 1) For types like strings, boxed types...

Prevent all the copies in FFI translation by having Rust types for GLib arrays, strings, hash table, lists, etc

2

See above. Those could implement all kinds of conversions to the actual Rust types, e.g. via Iterator::collect() for arrays, but use the GLib allocator for memory management. These could be...

Reduce usage of BoolError for manual code

6

We have quite some manual code where we currently use `BoolError` although there are multiple, proper error cases. For example `ObjectExt::set_property()` or all the signals related functions. I would suggest...

Create tests for glib/src/translate.rs

5

It would be good to have tests for the different translations from/to C in `translate.rs`, especially the container and pointer translations. This would be a good newcomer task. I'd start...

Use once_cell::Lazy instead of std::sync::Once

4

See summary. Simpler and less easy to get wrong.

Add derive macro for structs representing GObject properties

2

Kind of related to https://github.com/gtk-rs/glib/issues/637 and I would do them together in a few days. I'll write out the whole plan here once I'm at a computer again, but the...

Deriving Clone on ObjectSubclass is unsound

8

It would create a clone of just the instance private struct. Calling `ObjectSubclass::get_instance()` on it would then get a reference to some random memory. This needs to be prevented somehow....