Open matt77hias opened 4 years ago
Old issue but apparently float16_t, int16_t and uint16_t are valid when you use https://github.com/microsoft/DirectXShaderCompiler/wiki/16-Bit-Scalar-Types. So guess I'll add them to my types branch
Added support for int16_t and uint16_t to my type branch. Float16_t is also supported the same way.
Could it be possible to add or extend the display items, for which the style can be customized, to include the following:
P.S.: Imho, I do not really see the need for both a complete and separate set of C/C++ (Visual Studio) and HLSL (HlslTools) display items. The latter could fallback to the corresponding C/C++ display items for everything except the
Pack Offset
,Register Location
andSemantic
. I do notice that HlslTools provides more fine-grained customization for certain constructs (e.g.,struct
vsclass
), which is cool but practically not useful in combination with C/C++ due to the inconsistency between the two. Just some personal thoughts :-).Edit: I am wrong about the macro styles, as the actual cause is due to the includes nothing being resolved by the IDE (but are ok for the compiler). Cfr.: https://github.com/tgjones/HlslTools/issues/22