Making it easier to work with shaders https://git.yummers.dev/slang.git/atom?h=master 2025-05-17T02:26:44+00:00 2025-05-17T02:26:44+00:00 Jay Kwak 82421531+jkwak-work@users.noreply.github.com 2025-05-17T02:26:44+00:00 urn:sha1:d58243d9041947c99f18b82385e62c082507decb The user can explicitly use Vulkan memory model, or it will be automatically used when cooperative-matrix is used. When vulkan memory model is used, two keywords, "Coherent" and "Volatile", are not allowed. There are many differences regarding atomic and texture but this PR has changes limited to support `globallycoherent` keyword. When variables with `globallycoherent` is used with `OpLoad`, it will use additional options, `MakePointerAvailable|NonPrivatePointer`, that will provide the same effect. For `OpStore`, it will use `MakePointerVisible|NonPrivatePointer`. 2025-04-24T04:41:30+00:00 Harsh Aggarwal (NVIDIA) haaggarwal@nvidia.com 2025-04-24T04:41:30+00:00 urn:sha1:b78a8ba006fc9253cd1fd88fb7dd1eacfa749dfa * Fix #6544: Properly format nested type names in extensions Modify DeclRefBase::toText to properly handle types defined in extensions by qualifying them with their parent type name. This ensures getFullName() returns the full name like 'FullPrecisionOptimizer<half>.State' instead of just '.State'. Also handle other nested types in structs/classes similarly. * Update extension reflection handling - with generics args and namespaces - stopping namespace inclusion for extension members - Update to use getTargetType() to handle the generic arguments - update test cases * Simplify code to remove using parentDecl