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
{{ message }}
This repository was archived by the owner on Jun 16, 2020. It is now read-only.
The Clang ObjC importer in Swift 3 does a transform that breaks the recommended key generation ("".M().y().S().e().c().r().e().t().K().e().y()).
In order to automatically comply with the new API guide lines (which says that you should start any non-type with a lowercase letter), the importer transforms the functions for uppercased letters to lowercase, which conflicts with the lowercase letter functions.
Unfortunately, because of the typical length of keys put through your code, the Swift compiler spins into a deep loop and never finishes compiling.
Side note: Because you expose the letter functions as functions instead of properties, they become almost unreadable in Swift (any version). It seems a simple solution to change them from e.g. - (NSString *)a; to @property(readonly, copy) NSString *a;, which would make Swift read the same as ObjC.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The Clang ObjC importer in Swift 3 does a transform that breaks the recommended key generation (
"".M().y().S().e().c().r().e().t().K().e().y()
).In order to automatically comply with the new API guide lines (which says that you should start any non-type with a lowercase letter), the importer transforms the functions for uppercased letters to lowercase, which conflicts with the lowercase letter functions.
Unfortunately, because of the typical length of keys put through your code, the Swift compiler spins into a deep loop and never finishes compiling.
To read more about the change, see https://github.com/apple/swift-evolution/blob/master/proposals/0005-objective-c-name-translation.md and search for
Lowercase values
.Side note: Because you expose the letter functions as functions instead of properties, they become almost unreadable in Swift (any version). It seems a simple solution to change them from e.g.
- (NSString *)a;
to@property(readonly, copy) NSString *a;
, which would make Swift read the same as ObjC.The text was updated successfully, but these errors were encountered: