going forward will it stop working always when a new Swift syntax is introduced? It shouldn’t be a problem if the “problematic” part is skipped but we experienced a different behavior; the tool failed to complete the analysis and always exited with an error.
Hi @janc, thank you for your feedback, and welcome to the Sonar community!
As you probably guessed, the Swift analyzer has a parser that follows the versions of Swift. And after the announcement of a new version, we need to implement the new language constructs.
Unfortunately, the parser can’t recover from a parsing error. So, a file using features introduced after the latest version of Swift supported in SonarCloud may generate errors, and the analysis will then stop for that file.