4 ms·
It may also have been rushed due to the ABI stability deadline. I'm speculating, but it is easy to imagine that the SwiftUI team saw the window for getting new
by gwking 7y ago
It may also have been rushed due to the ABI stability deadline. I'm speculating, but it is easy to imagine that the SwiftUI team saw the window for getting new language-level features closing.
More generally, Apple's yearly splash model seems to dictate that teams either release or wait 12 months, if waiting is even an option at all. It makes me wonder how many Apple APIs would have been revised under a more flexible release model.
- skohan 7y ago> is easy to imagine that the SwiftUI team saw the window for getting new language-level features closing. Would function builders have much impact on ABI stability? My assumption was that they are essentially just a front-end transform: i.e. the SIL generated from a function builder would be equivalent to writing it out "long hand" - the same way that Codables can essentially be thought of as the compiler writing out boilerplate Swift code for you.
- plorkyeran 7y agoI think the yearly release schedule is the big issue. SwiftUI was pushed out a bit too early IMO, but it wasn't a year early so I totally get why they released it this year.