ranfdev

To clarify the problem here... Ideally we would do: ```rust // Specialized impl for Default types impl HasParamSpec for MyEnumType where Self: Default { type BuilderFn = fn(&str) -> ParamSpecEnumBuilder;...

That requires adjusting the macro specifically to support Enums. That means other external types requiring a default value will not take advantage of this. But yeah, that could work!

Problem: the macro doesn't know at compile time if the property is an Enum, so I can't write ``` if type.is_enum() && there_is_default_attribute { call_builder_with_default(default_attribute_value) } ``` So we are...

Inspired by that idea, I've tried to do ```rust // unless a custom `default` attribute is specified, the macro will use this trait. pub trait HasParamSpecDefaulted: HasParamSpec + Default {...

The number of changes is impressive. I agree with @GuillaumeGomez that we should evaluate if it's worth porting everything to this macro or not. Mainly because contributing to glib-macros would...

Weird. I haven't tested with ACLs, maybe there's something wrong going on... I will test

I appreciate it. Though I wouldn't save the bookmarks to a toml file. I'd keep a .gemini format. Bookmarks are a list of links anyways and Gemini can fully describe...

If there's an automatic migration, I approve

What's the advantage of using the syntax `[bookmark.$i]` instead of `[[bookmarks]]` (array of tables, https://toml.io/en/v1.0.0#array-of-tables)?

I think the `[[bookmarks]]` syntax makes it easier to edit the file by hand, because the user doesn't have to manually track which id is already used. But in 99.99%...