7 Commits

Author	SHA1	Message	Date
Ted Kremenek	3da51018b6	Teach ClangImporter to handle effective Swift version with minor release. ... Needed to support Swift 4.2.	2018-03-23 00:30:44 -07:00
Jordan Rose	a16d8a73d1	Bump the compiler version to 4.2 (and 3.4) (#13767) ... https://swift.org/blog/4-2-release-process/	2018-03-02 18:09:45 -08:00
Ewa Matejska	1272cd3aac	Making master call itself 4.1, updating the swift 3 compatiblity mode to be 3.3 (from 3.2), adding ability to pass swift-version 5. Importer work not done yet.	2017-08-17 20:57:01 -07:00
David Farler	b7d17b25ba	Rename -parse flag to -typecheck ... A parse-only option is needed for parse performance tracking and the current option also includes semantic analysis.	2016-11-28 10:50:55 -08:00
Graydon Hoare	5cf343f8f6	Logically compare swift versions as though X == X.0 == X.0.0, etc.	2016-10-24 20:23:02 -07:00
Graydon Hoare	ace9e7733d	Make 4.0 a valid effective language version.	2016-10-12 11:21:27 -07:00
Graydon Hoare	8970d44675	Add "-swift-version <n>" that sets LangOpts.EffectiveLanguageVersion. ... This flag switches the "effective language version" of the compiler, at least to any version supported (as of this change: "3" or "3.0"). At the moment nothing uses it except the language version build configuration statements (#if swift(...)) and various other places that report, encode, or otherwise check version numbers. In the future, it's intended as scaffolding for backwards compatibility. Fixes SR-2582	2016-09-20 15:11:37 -07:00