Allow codegen for UniformSetCacheRD for godot >=4.3

[Yarwin]

• UniformSetCacheRD has been reintroduced by godotengine/godot@5a988456

[Bromeon]

What does "reintroduced" mean here? Do we need to explicitly delete it (as you return true)?

[Bromeon]

Could you point to the PR rather than the commit here?

[Yarwin]

done

[Bromeon]

Is the #[cfg(since_api = "4.3")] necessary? If it's absent from all versions, we can just take it into the lower list, inside match (including comment).

[Yarwin]

Massive brainfart on my side – it should return "false" (this type is NOT deleted since 4.3, it was exposed by accident in 4.1) 😬
Fixed

[Bromeon]

Edit: misunderstood, makes sense.

[GodotRust]

API docs are being generated and will be shortly available at: https://godot-rust.github.io/docs/gdext/pr-816

[Bromeon]

I wonder if we should still move it down to the match statement, to avoid 2 conditions for the same class. It would also make it very obvious under which circumstances a class is deleted. Same for ThemeDB.

So we would have the following, please copy-paste if possible:

 match godot_ty {
        ... // all the existing stuff
        | "ResourceFormatImporterSaver"
        => true, 

        // Previously loaded lazily in 4.2 it loads at the Scene level. See https://github.com/godotengine/godot/pull/81305.
        | "ThemeDB"
        => cfg!(before_api = "4.2"),

        // Reintroduced in 4.3, see: https://github.com/godotengine/godot/pull/80214.
        | "UniformSetCacheRD"
        => cfg!(before_api = "4.3"),

        _ => false
}

[Bromeon]

Sorry for nitpicking, but I explicitly asked to copy-paste because there are several capitalization/period problems 😉

The empty line before the comment is removed by rustfmt? If yes, that's fine, but please refer to my code block suggested above, regarding the comment wording/formatting.

[Bromeon]

Still a capitalization issue with "reintroduced", but I'll fix this later, takes too much time for both of us otherwise 😉

Thanks a lot for the PR!