OK, filed 49768782.
The experience of using Xcode with this long standing glaring bug and having to file a radar for it has made me so frustrated that I had to include a little rant in the radar.
And another one here.
I'm baffled by the fact that this bug wasn't fixed in Xcode 10.2. To me, this is the most irritating thing about Xcode. How can it pass even the most basic QA checks?
It makes me wonder what process/culture within Apple it is that prevents bugs like this from just being quickly noticed and fixed.
Does fixing any bug, even very noticeable ones like this, always require end users to go through the soul-crushing trouble of filing radars?
Given that 99.9% of all users are probably even less inclined than me to file radars, I would not be surprised if my radar turns out to not be a dup which, I worry, will result in it getting low priority.
Are Apple using something else than Xcode for writing Swift code?
This is similar to a car manufacturer not noticing that an updated car model looses power steering after using the breaks, or waiting for sufficiently many customer complaints before fixing it, minus the risk of personal injury etc.