[FEATURE REQUEST] Rename ToValue::value_type or ParamSpec::value_type

[kawadakk]

ParamSpec implements ToValue, and both provide methods named value_type, which can lead to a surprising method resolution behavior when calling value_type with a method call syntax.

use glib::prelude::*;
glib::object::ObjectClass::from_type(gio::Application::static_type())
    .unwrap()
    .list_properties()
    .iter()
    .filter(|spec| spec.name() == "application-id")
    .inspect(|spec: &&ParamSpec| assert_eq!(spec.value_type(), glib::ParamSpec::static_type()))
    //                                          ^^^^^^^^^^^^^
    //                                          `<&ParamSpec as ToValue>::value_type`
    .for_each(|spec: &ParamSpec| assert_eq!(spec.value_type(), glib::Type::STRING));
    //                                          ^^^^^^^^^^^^^
    //                                          `ParamSpec::value_type`

[sdroege]

That makes sense. I think it should be ToValue::value_type() that should be renamed as that one is very unlikely to be called by user code.

Do you have any suggestions how to call it instead? @bilelmoussaoui @GuillaumeGomez @pbor you maybe?

[GuillaumeGomez]

Not really... ^^'

[kawadakk]

How about ToValue::type_in_value()? ("Type of Self in the Value form")

This is based on the observation that a Rust value converted to glib::Value may take a different form (e.g., String and &str turn into G_TYPE_STRING that is a pointer to a null-terminated g_malloc-allocated string).