anchor.diff:   ** All sub-rects allowed? In all use cases (RTs for example)?
    * Memory access granularity
    ** Writing concurrently to different areas of same memory backed by same/different image or view
  -
  -[source,c]
  -----
  -typedef struct {
  -    VkChannelSwizzle                            r;
  -    VkChannelSwizzle                            g;
  -    VkChannelSwizzle                            b;
  -    VkChannelSwizzle                            a;
  -} VkChannelMapping;
  -
  -typedef struct {
  -    VkImageAspect                               aspect;
  -    uint32_t                                    baseMipLevel;
  -    uint32_t                                    mipLevels;
  -    uint32_t                                    baseArraySlice;
  -    uint32_t                                    arraySize;
  -} VkImageSubresourceRange;
  -
  -typedef struct {
  -    VkStructureType                             sType;
  -    const void*                                 pNext;
  -    VkImage                                     image;
  -    VkImageViewType                             viewType;
  -    VkFormat                                    format;
  -    VkChannelMapping                            channels;
  -    VkImageSubresourceRange                     subresourceRange;
  -} VkImageViewCreateInfo;
  -
  -VkResult VKAPI vkCreateImageView(
  -    VkDevice                                    device,
  -    const VkImageViewCreateInfo*                pCreateInfo,
  -    VkImageView*                                pView);
  -----
   
    * Image views of all (valid) types and formats can be created from all (compatible) images
    * Channel swizzles
  
positive.code:  * +cmdBufferCount+ = 0
   * Submitting empty VkCmdBuffer
  
  [source,c]
  ----
  VkResult VKAPI vkQueueSubmit(
      VkQueue                                     queue,
      uint32_t                                    cmdBufferCount,
      const VkCmdBuffer*                          pCmdBuffers,
      VkFence                                     fence);
  ----
  
  .Spec issues
   * Can +fence+ be +NULL+ if app doesn't need it?
  
  
negative.code:  ** Queries
   * Large passes that may require tiler flushes
  
  Device initialization
  ---------------------
  
  Device initialization tests verify that all reported devices can be created, with various possible configurations.
  
   - +VkApplicationInfo+ parameters
     * Arbitrary +pAppName+ / +pEngineName+ (spaces, utf-8, ...)
  