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
If we have no plans to leverage the runtime flexibility that being an Obj-C subclass provides, it might make sense to make C4View (and any other classes) pure Swift classes to leverage some of the method dispatch and size improvements.
The text was updated successfully, but these errors were encountered:
Actually there are two things that use this: EventSource.swift for the on(..) methods and setValue(:forKey:) which I don't see being used. If we are ok to remove the event source stuff then we can do this @C4Framework?
If we have no plans to leverage the runtime flexibility that being an Obj-C subclass provides, it might make sense to make C4View (and any other classes) pure Swift classes to leverage some of the method dispatch and size improvements.
The text was updated successfully, but these errors were encountered: