Properly cast argument types in GLSL #785
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I was occasionally getting type errors around the
pow
function after #779. This appears to be because the type casting used inOutputExpressionList
was being omitted. For the other functions with an addedabs
call, I useOutputExpressionList
to recapture the previous casting behavior and forpow
I use the function's return type, ensuring that all arguments are expanded into vectors where possible.pow
in particular is often used in presets where the base or exponent is a scalar and the other argument is a vector.