When I leave the file, and do a build, the warning comes back. And the entire cycle repeats.
Now, I don't believe the warning is valid here, as I'm not capturing self in the closure. But what surprises me even more is the "when you look at it, it goes away" behaviour.
Is this a bug or in some way expected/intended behaviour? Should I file a radar?
BTW this is Xcode 15.4 / macOS 14.6.1. Strict concurrency checking is enabled.
Xcode dropping warnings — quite expected Xcode showing warnings where there is no warning — as well. Check via command line if the issue persists and if there is a warning from the compiler itself.
I see the same, but also with valid errors that disappear.
I have been tolerating it in the beta assuming there's some dependency mismatch with explicitly-built (or not) modules, or that a test build corrects errors from a target-only build by incorporating new modules -- and then leaving it for Xcode QA to sort out.
Consider also the apple developer forums when seeking support for Xcode - unless you can reproduce it on the command line using swift without Xcode.
Using Xcode 16.2 and I am also seeing this problem. During compilation, warnings are shown in the editor, but when the build is done, those disappear. If I go to the Report navigator, I can find the build in the list, and if I click on it, it opens the build log where I indeed can read any warnings/errors. But they no longer show in the editor like they used to in Xcode 15 and earlier.
Maybe I should wipe the Developer directory and try to rebuild everything? Or is there another way to easily clean any caches such that this could be fixed?
Xcode showing warnings where there is no warning — as well. Check via command line if the issue persists and if there is a warning from the compiler itself.