Many FFI functions that return multiple values should be replaced with implementations that return a struct providing meaningful information about the data. A tuple of strings is obtuse, and gir does not give us the tools to customize exactly how the Option<>s are encoded.
[ ] wp_link_get_linked_object_ids
[ ] can linked IDs be 0/missing somehow?
[ ] wp_metadata_find
[ ] also maybe wrap wp_metadata_set as .remove() and .add()? Option<> arguments make no sense in rust; if string type is the default, just provide MetadataEntry::with_string() or something.
Many FFI functions that return multiple values should be replaced with implementations that return a struct providing meaningful information about the data. A tuple of strings is obtuse, and gir does not give us the tools to customize exactly how the
Option<>sare encoded.wp_link_get_linked_object_idswp_metadata_findwp_metadata_setas.remove()and.add()?Option<>arguments make no sense in rust; if string type is the default, just provideMetadataEntry::with_string()or something.