Generic Components Expect Confusing Types

[scottbot95]

Problem

#385 added support for generic components, however when using rsx! to actually create a generic component, the type you pass as the generic parameter is the props type, not the "actual" generic argument of the component function. IE

#[derive(Props, PartialEq)]
pub struct TypedInputProps<T> {
    #[props(optional, default)]
    initial: Option<T>,
}

#[allow(non_snake_case)]
pub fn TypedInput<T>(_: Scope<TypedInputProps<T>>) -> Element
{
    todo!()
}

// TypedInput must be created like
TypedInput::<TypedInputProps<i32>> {}
// NOT with just i32 as would one would intuitively expect
TypedInput::<i32> {}

Expected behavior

I understand from a technical perspective it is simpler to just accept the props type directly in rsx! since one of the primary purposes of that macro is to create the props struct, however that behavior is confusing and unintuitive. It would be substantially more user-friendly and require less boilerplate if the generic args passed in rsx! simply matched the generic args to the component function itself.