There are a number of classes from upstream that don't #import <UIKit/UIKit.h> as they should. With Objective-C it doesn't matter as much since all GUI apps will bring this in, but with Swift and bridging headers, it can throw a build error unless you add the line to your bridging header. We should fix this. Anything which descends from UIKit should have an explicit import.
jonastreub
commented
9 years ago
There are a number of classes from upstream that don't
#import <UIKit/UIKit.h>as they should. With Objective-C it doesn't matter as much since all GUI apps will bring this in, but with Swift and bridging headers, it can throw a build error unless you add the line to your bridging header. We should fix this. Anything which descends from UIKit should have an explicit import.