[FEATURE REQUEST] properties macro: automatically prepend is_ on generated getter functions on bool properties

[SeaDve]

I believe it makes it more consistent with the generated bindings and it sounds more natural.

Example:

mod imp {
    #[derive(glib::Properties, Default)]
    #[properties(wrapper_type = super::Item)]
    pub struct Item {
        #[property(get, set)]
        pub(super) new: Cell<bool>,
    }

    ...
}

...

should have a generated getter of obj.is_new() instead of just obj.new().

[sdroege]

Why don't you name you property is-new then? As you say, that sounds much more natural :)

[SeaDve]

I keep it consistent with how the bindings handle bool properties like sensitive and visible, where the property name does not have is- prefix, but the getter function do. Not a big deal, but maybe something to consider.

[bilelmoussaoui]

I keep it consistent with how the bindings handle bool properties like sensitive and visible, where the property name does not have is- prefix, but the getter function do. Not a big deal, but maybe something to consider.

Right, except those are part of the C API that is being adapted to Rust

[sdroege]

There's also a lot of C API that prefixes the property names. is- has- etc.

[SeaDve]

I guess it is not worth it then to make the macro more complex just for this, I think I'll close this

[yuraiz]

I want to have loop property to be consistent with gtk::MediaStream, but I can't use it with Properties macro
I suggest to allow getter and setter renaming

[yuraiz]

Or it's possible to use is or has keywords instead of get

[bilelmoussaoui]

Or it's possible to use is or has keywords instead of get

No. Please name your properties as wish them to be named. Regarding naming your property as loop, see #1067

[yuraiz]

But I want setter to have normal name set_loop

[yuraiz]

is prefix is used for many places in standart library: https://doc.rust-lang.org/std/?search=is_