TSL: Respect types in WGSL Layouts

[RenaudRohlinger]

Maybe Related: #28659 #28577

Description
The regex function in the parsing method of WGSLNodeFunction was not taking in account the <abc> part resulting in not respecting the type properties. For example the type of vec2<ivec2> would be converted to vec2 instead of ivec2.
This PR fixes the issue.

This contribution is funded by Utsubo

[sunag]

type of vec2 would be converted to vec2 instead of ivec2

Did you mean: vec2<i32> would be converted to ivec2 instead of vec2?

The PR broke the webgpu_tsl_interoperability, I think it is related to texture_2d<f32>

[RenaudRohlinger]

It's probably another issue unveiled from this fix that was luckily working?

The issue only appears with wgslFn and works fine in TSL, it seems to generates a vec4 var in the example instead of simply consuming it as a texture:

[sunag]

The issue only appears with wgslFn and works fine in TSL, it seems to generates a vec4 var in the example instead of simply consuming it as a texture:

This can happen if the type is texture_2d<f32> instead of texture_2d. These sub-type are ignored WGSLNodeFunction to optimize the checking in WGSLNodeBuilder.

[cmhhelgeson]

The issue only appears with wgslFn and works fine in TSL, it seems to generates a vec4 var in the example instead of simply consuming it as a texture:

This can happen if the type is texture_2d<f32> instead of texture_2d. These sub-type are ignored WGSLNodeFunction to optimize the checking in WGSLNodeBuilder.

Not just in texture_2d, but pretty much any type that is not a fundamental data type like a vector, primitive type, or matrix type. Additionally, for some reason, when a texture_2d was added as an input rather than a texture_2d, an additional mat3x3 uniform was added to the wgsl objectStruct. I haven't investigated why however.

[RenaudRohlinger]

From what I understand and saw on the WebGPU specs a condition as simple as:

if ( resolvedType.startsWith( 'texture' ) ) {

resolvedType = type.split( '<' )[ 0 ];

}

Should be enough to support all non-fundamental data (mostly texture/texture_storage) in the node builder.
Consequently I counter reverted the #28577 and now all examples seems to work with proper types handled.

/cc @sunag @cmhhelgeson

[sunag]

Merging... thanks!