on other attributes, we should `hlsl_fixme()`, because (AFAIU) there is at least an attribute that could change the semantics if ignored (e.g., `allow_uav_condition`). We could `hlsl_warning()` for the attributes we already consider relatively safe to ignore.
Yes, I agree with this part. v4 had it as hlsl_fixme().
In general I think we should put in the effort to avoid ever emitting invalid bytecode.