From a136586a339032126540ceb24f7c3f15eaba68c8 Mon Sep 17 00:00:00 2001 From: David Robillard Date: Fri, 20 May 2022 19:44:20 -0400 Subject: Use consistent integer types for view positions and sizes Actual window sizes and positions fit easily in a 16-bit integer. So, we use that in "representation contexts" like events. This makes structures smaller, and allows the values to be converted to float, double, or integer without casting (since any int16_t or uint16_t value can fit in them without loss). Setter APIs use native integers for convenience, to avoid casting hassles when doing arithmetic. Ranges are checked at runtime. --- doc/conf.py.in | 1 + 1 file changed, 1 insertion(+) (limited to 'doc') diff --git a/doc/conf.py.in b/doc/conf.py.in index b208553..1d5923a 100644 --- a/doc/conf.py.in +++ b/doc/conf.py.in @@ -24,6 +24,7 @@ _opaque = [ "VkInstance", "VkResult", "VkSurfaceKHR", + "int16_t", "size_t", "uint16_t", "uint32_t", -- cgit v1.2.1