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
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:/