With few exceptions, this project aims to simulate whatObjective-Ccode is translated to in assembly(i.e. calls to`objc_msgSend`, inserted ARC functions, literal class-refs in class method calls, etc) as opposed to mirroring Objective-C style code and dynamism, which Swift cando alreadyby using`@objc` classes.

With few exceptions, this project aims to simulate, in Swift, howObjective-Cworks under the hood(i.e. calls to`objc_msgSend`, inserted ARC functions, literal class-refs in class method calls, etc), as opposed to mirroring Objective-C style code and dynamism which Swift canaccomplish alreadyvia`@objc` classes.

This project could theoretically be used as a dynamic runtime backend for a transpiled progamming language to transpile to, and as such, this framework and its conventions were crafted withthatin mind. Many of the constructs here may seemlike anything buttype-safe, butit's all perfectly safe if the code is generated by some other, more type-safe language.

This project could theoretically be used as a dynamic runtime backend for a transpiled progamming language, and as such, this framework and its conventions were crafted withthis ideain mind. Many of the constructsusedhere may seemto lacktype-safety, buteverything is perfectly safe if the code is generated by some other, more type-safe language. In short, this code is not meant to be written by hand if used for anything serious.