How we built an interpreter for Swift
bitrig.app
How we built an interpreter for Swift
1–10 of 39 posts
Re: How we built an interpreter for Swift
#2Re: How we built an interpreter for Swift
#3Re: How we built an interpreter for Swift
#4Re: How we built an interpreter for Swift
#5Your website won't let me scroll to see the content on Firefox Android
Re: How we built an interpreter for Swift
#6Does SwiftUI have properties that uniquely make this type of interpreted system possible, or could it also use UIKit under the hood? On the surface, it seems like UIKit might be more difficult since you’d probably need to parse all of the obj-c header files in addition to the .swiftinterface.
Very cool stuff, excited to follow along how you all develop the product!
Re: How we built an interpreter for Swift
#7This is fascinating work, amazing job to the team! Does SwiftUI have properties that uniquely make this type of interpreted system possible, or could it also use UIKit under the hood? On the surface, it seems like UIKit might be more difficult since you’d probably need to parse all of the obj-c header files in addition to the .swiftinterface. Very cool stuff, excited to follow along how you all develop the product!
Re: How we built an interpreter for Swift
#8Your website won't let me scroll to see the content on Firefox Android