Christoffer Lerno
Christoffer Lerno
Should be fixed now.
That would break things like ```c int[] x = foo(); int[] y = x * 3 + 1; // int[] y = x * (int[])3 + (int[])1; ```
I think this is fine in GLSL though?
If we think about how casts work: 1. First we have the normal casts, for example between binary sub expression. 2. Then we have the assign expression, here there is...
For what it's worth, HLSL always does the scalar conversion: https://microsoft.github.io/hlsl-specs/specs/hlsl.pdf
If you just want it explicit for parameters, then that's something I could consider. I think the conversions in expressions is important, but conversion passing it as arguments.. that's a...
I found another issue with unions as well, not quite the same but related. `@align` is a bit under-tested. I added some test cases, but I feel there might be...
Well, yes that can happen too.
So the reason this happens is that these are the two types generated: ``` %Test = type { ptr, [8 x i8] } %Test2 = type { %Test, i32 }...
Oh, and I added an additional unit test for it to test the runtime size. If you want to add more tests (those that pass are fine, they are important...