Open brianquinlan opened 2 years ago
Hmmm. This should happen automatically. Maybe the definition of NSString in the internal headers is doing something weird, and not explicitly extending NSObject?
I suppose we can hard code this behavior.
The declaration for NSString looks like:
@interface NSString : NSObject <NSCopying, NSMutableCopying, NSSecureCoding>
Hmmm... yeah, I see that this usually works but didn't for NSString for some reason.
Objective-C interfaces are converted to Dart classes that extend _ObjCWrapper e.g.
Instead, they should extend their actual superclass e.g.
Otherwise
NSString
cannot be passed whenNSObject
is expected.FYI,
castFrom
can be used as a workaround.