readonly_and_readwrite_storage_textures

Check navigator.gpu?.wgslLanguageFeatures?.has('readonly_and_readwrite_storage_textures') before choosing a shader that uses this language feature. It is available automatically when supported; requires readonly_and_readwrite_storage_textures; documents the dependency and rejects the shader on unsupported implementations. This language token is not a requiredFeatures entry for requestDevice(); any additional device requirements are described below.

A storage texture can be declared with an access mode such as texture_storage_2d<r32float, read_write>, allowing both textureLoad and textureStore through that resource. This language extension also adds textureBarrier() for ordering storage-texture memory accesses within a compute workgroup.

Image-processing and simulation kernels can use these access modes to work with storage images directly. The host-side bind-group layout uses "read-only" or "read-write", while WGSL spells those modes read and read_write. The texture must have STORAGE_BINDING usage, and its format must support the requested access; texture-formats-tier2 expands the read-write choices.

The extension does not make texture updates atomic or synchronize different workgroups. Use distinct input and output images for algorithms with overlapping updates, or divide work into separate dispatches. On older language implementations, a sampled input texture and a write-only storage output provide a common fallback.