Marco ArmentTranslation: "You screwed up somewhere in this entire file. Figure it out yourself. Good luck! đ¤ˇâ
It's the "Segmentation faultâ of the modern era.
iâm unable to type-check YOUR expression in reasonable time
(The actual problem, 67 lines below the error message: .disabled() needs to be applied to the Button, not the ToolbarItem, which I had to figure out by just commenting out random stuff until it compiled.)
Maybe some of these new "intelligences" can be used to make SwiftUI's error messages useful
Matt Birchler@marcoarment AI can do a lot of things, but this may be an impossible task.
Peter van Broekhoven@marcoarment âHere's what I found on the web for âThe compiler is unable to type-check this expression in reasonable time; try breaking up the expression into distinct sub-expressionsââ
Tom Jacob@marcoarment tbh why canât apple intelligence be used to give better error messages? Canât it suck in your code, whatever it can from the compiler and give a probabilistic idea of whatâs going wrong?
Mieszko Ĺlusarczyk@tomjacob @marcoarment Maybe, but it may get the answer wrong - would that help?
@spitfire @marcoarment perfect is the enemy of good, I agree.
@tomjacob @marcoarment I am using LLMs from time to time. Sometimes they help me do something, sometimes they lead me down some crazy path and waste my time by inventing stuff that does not exist and confidently giving me the wrong answer which ultimately wastes my time:/
Tomer Shemesh@marcoarment I actually have had a surprising amount of success when these errors happen just copying the entire file into ChatGPT or CoPilot and asking it to find the error for me.
SĂśren@marcoarment OK! Playing âSheâs My Typeâ by Kurt Reston
Jeff@marcoarment Iâd rather have useless messages than âconfidently wrongâ messages
@marcoarment Oof, you donât want an LLM in your compiler.
Steve Tibbett@marcoarment If you just dropped the file with the error into Claude, does it detect the error? Having it diagnose an error automatically could quite possibly be great.
Owen Mathews@marcoarment equally frustrating is when it canât correct simple syntax errors in imperative code blocks inside a view builder. Iâve been bit by simple things like a missing colon in a switch statement.
Tim Schmitz@marcoarment I'm glad I'm not the only one who debugs that error this way đ¤Śââď¸
Wayne Dixon@marcoarment sadly, that seems to be the only way to debug the error. Iâve had to do that too many times to count.
Michael Rowe@marcoarment I feel randomly commenting out code helps a lot with SwiftUI ;)
Joao Dordio@marcoarment this is all very much plausible and warranted for.
Stuart Isaac@marcoarment the hard lesson Iâve been learning from this (particularly with toolbar) is to put anything non-trivial into a separate computed property so Xcode can figure it out
Allen Pike@marcoarment For a simple API-typo issue like this, in an IDE like Cursor.sh in a language like Python or TypeScript, nowadays you would get an underline "fix this" that would indeed fix it (or maybe even a tab-complete suggestion to fix it)
Harish@marcoarment this blog explains the problem well. https://danielchasehooper.com/posts/why-swift-is-slow/
