3 ms·
If you look at it benevolently, then it seems like they tried to force out the API they wanted, and made it publicly available to verify, and then worked backwa
by setr 6y ago
If you look at it benevolently, then it seems like they tried to force out the API they wanted, and made it publicly available to verify, and then worked backwards to implement it in the compiler properly
That is, "So at least now, nothing is preventing other people to try to replicate in a open source manner those features." was always the intent
Similar to rust implementing magic features and APIs, and macros, in nightly, before the API is verified and the implementation is ready.
In which case, you'd expect all of SwiftUI to be eventually possible by anyone else.