You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are several places where vulkan is less strictly typed than it could be, some examples;
Bytestring -> ExtensionName
Bytestring -> LayerName
Word32 -> QueueFamilyIndex
...
Some of this could be gleaned automatically from the spec (from the parameter name), however some amount of it would have to be manual.
The goal would be that, excluding places with manual type annotations, existing programs would still work.
The advantages are pretty clear, the drawback is that it would be getting a little further away from the spec as written, and incorrect (or missing) newtypes would be very confusing.
The text was updated successfully, but these errors were encountered:
There are several places where
vulkan
is less strictly typed than it could be, some examples;Some of this could be gleaned automatically from the spec (from the parameter name), however some amount of it would have to be manual.
The goal would be that, excluding places with manual type annotations, existing programs would still work.
The advantages are pretty clear, the drawback is that it would be getting a little further away from the spec as written, and incorrect (or missing) newtypes would be very confusing.
The text was updated successfully, but these errors were encountered: