Skip to content

Finish removing -swift-version 3 #20409

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed

Conversation

slavapestov
Copy link
Contributor

Fixes rdar://problem/43101816.

@slavapestov
Copy link
Contributor Author

@swift-ci Please test

@slavapestov
Copy link
Contributor Author

@swift-ci Please test source compatibility

@swift-ci
Copy link
Contributor

swift-ci commented Nov 7, 2018

Build failed
Swift Test OS X Platform
Git Sha - 058b29e

@swift-ci
Copy link
Contributor

swift-ci commented Nov 7, 2018

Build failed
Swift Test Linux Platform
Git Sha - 058b29e

@slavapestov slavapestov requested a review from tkremenek November 7, 2018 22:45
@@ -153,7 +153,7 @@ class Version {
// List of backward-compatibility versions that we permit passing as
// -swift-version <vers>
static std::array<StringRef, 4> getValidEffectiveVersions() {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Array size should be 3 instead of 4

Suggested change
static std::array<StringRef, 4> getValidEffectiveVersions() {
static std::array<StringRef, 3> getValidEffectiveVersions() {

@benrimmington
Copy link
Contributor

See also #20374

@slavapestov
Copy link
Contributor Author

Oops, I didn't realize we made the same change here. @tkremenek The only significant difference I see is that I removed the swift3 lit substitutions from lit.cfg, and XFAILd the offending tests. Do you want to take over?

@tkremenek
Copy link
Member

Yeah I'll take over.

@slavapestov
Copy link
Contributor Author

Thanks Ted!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants