We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Affected tests:
tests/language-feature/enums/strongly-typed-id.slang
==
Example output:
WGPU error: Error while parsing WGSL: :25:8 error: no matching overload for 'operator == (u32, i32)' 2 candidate operators: • 'operator == (T ✓ , T ✗ ) -> bool' where: ✓ 'T' is 'abstract-int', 'abstract-float', 'f32', 'f16', 'i32', 'u32' or 'bool' • 'operator == (vecN<T> ✗ , vecN<T> ✗ ) -> vecN<bool>' where: ✗ 'T' is 'abstract-int', 'abstract-float', 'f32', 'f16', 'i32', 'u32' or 'bool' if(id_1 == i32(4)) ^^^^^^^^^^^^^^ - While validating [ShaderModuleDescriptor] - While calling [Device].CreateShaderModule([ShaderModuleDescriptor]).
The text was updated successfully, but these errors were encountered:
I have a fix that adds some WGSL legalization for the issue described here.
However, that just revealed a similar issue for mismatching return value types. I'll create a fix for that as well, as part of this issue.
Sorry, something went wrong.
Fix operator signedness mismatch issue
c44786b
This helps to address issue shader-slang#5606.
wgsl: Insert casts for integer type return values
93330ed
This closes shader-slang#5606.
wgsl: Fix signedness mismatch issues
ffe3b87
This fixes signedness mismatch issues for: - Binary operators - Return values This closes shader-slang#5606.
aleino-nv
Successfully merging a pull request may close this issue.
Affected tests:
tests/language-feature/enums/strongly-typed-id.slang
(operator==
, signed/unsigned mismatch)Example output:
The text was updated successfully, but these errors were encountered: