@zfigura I think that the native compiler throwing an error with multiple compatible function overloads with "float" vs "float1" arguments is an exception rather than the rule and we should indeed revert the patch to make more applications work.
It's not so much that native never prioritizes an exact match—certainly there's *some* prioritization logic—but more that it doesn't *always* prioritize an exact match. I.e. the rules are more complicated than that, and, as Giovanni says, I think we'd rather reject valid programs with a hlsl_fixme(), than accept invalid ones.