Basic types

[filnet]

This PR is a follow up of #1134. Not sure what is the accepted way of contributing to someone else's PR.

Changes include:

• Rename the new Basic::Vulkan enum to Basic::Typedef.
  Vulkan-1.0.gir currently contains only what can be considered as typedef records.
  See https://gitlab.gnome.org/GNOME/gobject-introspection/-/blob/main/misc/update-vulkan-gir.py#L17
• Hack the parser to produce Basic::Typedefs when parsing the Vulkan namespace.

So a bit more generic and the const VULKAN: &[&str] = &[...] is gone. :)

[filnet]

A next step would be to address the Vulkan specific hack.

We need a cleaner way to trigger the "special" handling of Vulkan records:
1/ could be based on a new flag in the Record itself (or based on the state of the Record)
2/ could be globally enabled in the Vulkan-1.0.gir file (via meta data or something else)
3/ could be globally enabled in the consumer Gir.toml file when declaring the external library
4/ could be enabled in gir itself (like now but in a "better" way via extension/plugin/what not).

[filnet]

We probably won't keep this assert but it shows that Vulkan records are incomplete.
Unfortunately, non Vulkan records can be incomplete too so we can't use is_incomplete as the trigger for the new behavior.

And then there is the problem of the "ash::vk::{}" format string: where should it be specified if we want to externalize it (to make gir Vulkan agnostic again).

[filnet]

An alternative approach to mapping the names with "ash::vk::{}" would be to not do it and, instead, generate rust type aliases in a post process step.

pub type vulkan::Bool32 = VkBool32;

Advantage is that the Vulkan namespace will not be erased anymore (less "magic").

Disadvantage is that a bit more rust code will be generated.

[filnet]

Likewise, instead of tweaking the Vulkan namespace on the fly, we could introduce a postprocess hook that tweaks/transforms the namespace after it was parsed.

[filnet]

I went with post processing the Vulkan namespace.
And found src\custom_type_glib_priority.rs as example to follow.

[bilelmoussaoui]

What is the status of this one?

[MarijnS95]

@bilelmoussaoui I don't think we ever continued the discussion how to best map Vulkan-1.0.gir (not GstVulkan-1.0.gir) fundamental types in gir.