Casey LissI genuinely, truly enjoy SwiftUI. It has made my products **so much** better.
However, if I see “The compiler is unable to type-check this expression in reasonable time" one more time, I may drop-kick my computer.
((Jann Gobble)) 🏳️🌈@caseyliss Good idea. It'll give you a reason to buy a M4 Pro Mini!!! 😂 @siracusa
Jan Lehnardt 
@caseyliss -f-wait-unreasonable-time when?
Brandon Butler@caseyliss It would be really fun if you tried Flutter sometime :)
@caseyliss It could be fun. I can take you on an adventure :)
Jonathan D. Rhyne@caseyliss Search your feelings, you know it to be true.
Joseph Humfrey@caseyliss 💯!
I’ve developed ridiculous coping mechanisms, like binary searching for the error by commenting out half the code at a time until it compiles again 😫 (thankfully SwiftUI by its nature makes this part comparitively easy)
Manton Reece@caseyliss I'm honestly still new to SwiftUI, but already I think I'd prefer if the error was just: "You messed up a type declaration somewhere, but who knows where!"
@manton it wasn’t that! It was me not unwrapping an optional. Which, okay, fair enough, but I wish I had an actionable error message.
Alex Babaev@caseyliss @manton its almost always "some type is wrong or enum is written incorrectly", but it drives me crazy that it can't pinpoint the exact place.
Christian Kent 𝘊𝘒 :＼﹥?SYNTAX ERROR vibes
Steve BarnesTry breaking your expressions of anger into distinct sub-expressions.
Sören@Starfia @caseyliss I know this is a joke, but it sure would help if Xcode were better at refactoring. View too complex? Fine — offer me a fix-it that extracts a portion into a new file
@chucker –
Except that in my experience, "view too complex" is false. Usually it's just been some minor syntax thing like it was for Casey here.
Joseph Simpson@caseyliss On the bright side, if you drop-kick your computer you can get an M4 Max
Eshu Marneedi@caseyliss “Try breaking your expressions into distinct sub-expressions. :)”
WHAT EXPRESSIONS AM I SUPPOSED TO BREAK UP
Caleb Davenport@caseyliss a new, smaller, lighter mac mini would hurt your foot less
@calebd Such a company man
Kevin@caseyliss I tend to extract things not to different files (unless they will be reused) but to ViewBuilder computed properties to keep the size (complexity) of body small.
Tyler
Damian Mehers@caseyliss you’ll be seeing a lot more than one more time, so your computer is safe!
Rapha
Kyle Borah
Sören Gade@virtualrapha @caseyliss this made my day.
Jared Counts@virtualrapha @caseyliss I’m very new to iOS development, and I figured this wasn’t a real error when restarted Xcode could clear it
Nathan King
Thomas Sturm@virtualrapha @caseyliss Yes. So much yes.
Leo Dion
Leo Dion (@[email protected])
Attached: 1 video One of the biggest pains in Swift (and SwiftUI) is the "The compiler is unable to type-check this expression in reasonable time" While it's true it's not helpful. Besides explicitly declaring the type and breaking up your SwiftUI code, what else have you found helpful? In this episode @[email protected] and I discuss the joys and pains of Swift's type system. https://brightdigit.com/episodes/188-ludicrous-types-with-nick-lockwood
Adam Overholtzer@caseyliss I made this in case I got a ticket to wwdc: https://cottonbureau.com/p/4ZS7XZ/shirt/swiftui#/21368454/tee-men-premium-lightweight-heavy-metal-100percent-cotton-s
Marc Edwards@caseyliss And the preview pane fails so often. I hope SwiftUI gets a lot of solid improvements in 2025.
Adam Demasi@marcedwards @caseyliss Unfortunately, thinking it *has* to get better next year is why we’re still in this state of building apps with poor tooling. We’re at the 10 year mark of Swift and we’re dealing with a compiler that’s slower and more complex than it’s ever been, despite running on hardware that’s faster than ever. Huge respect for the dev tooling teams, but history has shown that we shouldn’t hold our breath for a miracle.
@kirb Yep, I agree with all of that. I’m mostly happy, but there are definitely areas that are not good enough. +@caseyliss