-
Notifications
You must be signed in to change notification settings - Fork 68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix error behavior for initialize_to_identity #651
Conversation
Previously, the specification said that a compiler must issue a diagnostic if the initialize_to_identity property was used without a known identity value. This requirement cannot be satisfied, because the presence of the initialize_to_identity value in a property_list cannot be proven until run-time. This change replaces the compile-time diagnostic with a run-time exception.
Good catch. I guess we can put this kind of stuff back when we have "compile-time properties". BTW, do we have a test on the CTS that we need to adjust? (aka compile time versus runtime error) |
Agreed.
I think so. I'm not very good at reading the CTS tests, but it looks to me like we only test valid uses of |
WG approved to merge |
Cherry pick KhronosGroup#651 from main (cherry picked from commit 8424248)
Fix error behavior for initialize_to_identity (cherry picked from commit 8424248)
Previously, the specification said that a compiler must issue a diagnostic if the
initialize_to_identity
property was used without a known identity value. This requirement cannot be satisfied, because the presence of theinitialize_to_identity
value in aproperty_list
cannot be proven until run-time.This change replaces the compile-time diagnostic with a run-time exception.