the dot() method is for walking down into a structure that is being validated eg: loc.dot(Field::pMemoryBarriers, 5).dot(Field::srcStagemask)

Begin the render pass, with subpass contents provided by secondary command buffers.

Common combo for most GPU-AV test

same as dot() but will mark these were part of a pNext struct

This function is a helper to know if the extension is enabled. Times to use it - To determine the VUID - The VU mentions the use of the extension - E

The word used to define the Instruction

VK_KHRONOS_PROFILES_UNKNOWN_FEATURE_VALUES in profiles can be used and future extensions can be put in here for testing

If you are using this, please leave a comment why, otherwise its hard to remove these once added

Designed for majority of cases that just need to simply add dynamic state

Will be updated once its known its valid SPIR-V

The reason we keep strings of ALL the VUIDs is to make it easier to search and know what is covered or not. The reality is the "action" commands (draw

Check if value is integer multiple of granularity

optional::has_value() Determines whether the `optional` contains a value. Returns `false` if and only if `*this` is empty.