This is the wrong way to go about it. The syntax is great, what is needed is updates to reflect modern hardware: -Vector types. (With arbitrary sizes not just

This is the wrong way to go about it. The syntax is great, what is needed is updates to reflect modern hardware: -Vector types. (With arbitrary sizes not just up to vec4 for like on GPUs) -New operators like clamp, and other intrinsic. (See GLSL and modern instruction sets) -Min/max: |< >| -Dot: -Cross product: >< -Swizzle: a.3.2.1.0 -Qualifiers for warping behavior. -Standard library with cash management hints. -Define qualifiers for padding of structs to be defined. I would also argue you could change some things in the spec to make it easier for compilers to optimize, like making the calling a switch without a catching case undefined behavior. As for the syntax itself, I could find being able to type multiple break commands in a row to get out of more then one loop useful, but its not a big thing. I would probably drastically restrict the power of the pre-processor too. (If you have too much time on your hands: https://www.youtube.com/watch?v=443UNeGrFoM https://www.youtube.com/watch?v=443UNeGrFoM)