[naga] Why do some properties have an extra underscore after their names are converted to WGSL?

[Fmansama]

For example, my Material_Texture2D_0 property has become Material_Texture2D_0_ and my Material_Texture2D_1 attribute has become Material_Texture2D_1_ I don't want the original attribute name to be changed, Is there a parameter that allows the tool not to change the property name?

[Fmansama]

[Fmansama]

Why is there an underline???

[Fmansama]

There is no underscore in the property name in the spv file, I don't know why there is an extra underscore after converting spv to wgsl.

[jimblandy]

This is not a bug, it is intended behavior. In general, Naga doesn't preserve the names of identifiers in the output. If you need a shader translator that preserves names, Naga does not meet your requirements, and you will have to use something else. However, I think you will find that most shader translators do rename identifiers in some circumstances.

In general, Naga cannot always give identifiers the same name in the output that they had in the input, because the scope of the item can change in translation. That is, even if two identifiers are in different scopes in the input, Naga may need to generate output that puts them in the same scope.

Naga's strategy for generating unique names is to take the user's identifier, clean it up, and add _N if there is more than one occurrence. So, for example, if the input uses the name x multiple times, Naga will name them x, x_0, x_1, x_2, ... in the output. But if the user already has their own identifer named x_2, then Naga's strategy will fail. To avoid this, Naga checks for such names, and adds an underscore to them. This is what is happening in your case: Naga is adding an underscore because your identifier ends with _N.

[Fmansama]

get it, thanks