Re: [PATCH v3 0/2] MR58: vkd3d-shader/hlsl: Reinterpret minimum precision types as their regular counterparts.

[Henri Verbeet (＠hverbeet)]

I'm not necessarily opposed to this, but like Zeb, this does make me a bit uneasy. (And hence the delay in review.) Part of the consideration is that HLSL compiler output may be stored and is potentially long-lived. The main questions I have at this point are the following:

- Concretely, how much time do you estimate implementing this properly would take?
  - Technically, wouldn't we need to work out casting rules anyway? This would affect what is considered valid HLSL input in the first place, not just what bytecode we end up producing for valid inputs.