You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
SR-1419 / SR-8894 documented this previously and were closed as intended behavior until SE-0192 was done.
In the section on C enums in SE-0192 it's mentioned that adding the `frozen` concept to the language would enable Swift to drop the `init(rawValue🙂` constructor behavior on imported enums that allows invalid values:
Apartfromtheeffectonswitches, afrozenCenum's init(rawValue:) will also enforce that the case is one of those known at compile time. Imported non-frozen enums will continue to perform no checking on the raw value.
The text was updated successfully, but these errors were encountered:
Additional Detail from JIRA
md5: 99c656495cc5a924a9caa22546e8d9d3
Issue Description:
SR-1419 / SR-8894 documented this previously and were closed as intended behavior until SE-0192 was done.
In the section on C enums in SE-0192 it's mentioned that adding the `frozen` concept to the language would enable Swift to drop the `init(rawValue🙂` constructor behavior on imported enums that allows invalid values:
The text was updated successfully, but these errors were encountered: