3

It seems Xcode is passive-aggressively encouraging me to switch to Swift 3.0. As I type code, and when I invoke a build, all kinds of warnings & errors relating to Swift 3.0 syntax show up, only to disappear once compilation finishes.

It seems the dynamic incremental compilation setting on the "left hand" is not talking to the static actual compilation setting on the "right hand".

It's very distracting. This is Xcode GM 8.1. Has anyone else experienced this and found a workaround?

BaseZen
  • 8,650
  • 3
  • 35
  • 47

1 Answers1

2

It's testing your inner strength 2.3 vs 3.0 knowledge. You have to stay firm and shtick to the syntax of the days of the yore. Consider that one of life's challenges. Do not give in to the 3.0 provocations. Cause if you show weakness for one single moment and give in there will be changes to undo to get it to compile with 2.3.

Stay strong. There is more yet to come. I think 8.2 beta will be dumped onto out unsuspecting heads shortly. [Ed: Indeed, already: https://developer.apple.com/library/prerelease/content/releasenotes/DeveloperTools/RN-Xcode/Introduction.html]

Anton Tropashko
  • 5,486
  • 5
  • 41
  • 66
  • I will upvote for humor but not accept it as the answer :-) – BaseZen Nov 04 '16 at 06:16
  • Thanks. To be fair to flying saucer employees, noone told them: you can scrap the eclipse extension and rewrite into an android studio that's finally useable(?). There is no iSteve to approve a radical move into: Xcode. The Spartan Edition. – Anton Tropashko Nov 04 '16 at 06:35