News for hackers. Stuff that matters.
Re:Roadmap for Improving the Type Checker by fingerlocks on Friday October 31, 2025 @04:21AM (#45769518)
Follow a couple of rules and this won’t happen.

Type annotate everything. Don’t mix integers and doubles, be explicit. Most important of all, do not ever make a long chain of nested result building function calls with those stupid trailing untyped dangling {} closures, especially when the closure expects an implicit return of an opaque ‘some’ type.

What I’m saying is, don’t use SwiftUI. It’s a pee filled kiddie pool to attract JavaScript react devs with awful performance and semantics.

Re:Roadmap for Improving the Type Checker by deliriumchn on Friday October 31, 2025 @06:01AM (#45770221)
Well apple themselves are pushing swiftUI and I suspect it will be the main (and only) approach as time goes on, even though its just a wrapper around "older" approach...
Re:Roadmap for Improving the Type Checker by rob74 on Friday October 31, 2025 @09:00AM (#45771511)
So then, another language which has lots of features, but if you are foolish enough to combine feature A, feature B and feature C, bad things will happen? C++ sends its regards...
Re:Roadmap for Improving the Type Checker by an0malous on Friday October 31, 2025 @09:17AM (#45771671)
That sucks because I really like the semantics of SwiftUI over UIKit. Declarative, reactive code just makes sense for UI.