Skip to content

[Space Engine] Remove the @_downgrade_exhaustivity_check hack #17764

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

Merged
merged 1 commit into from
Aug 24, 2018

Conversation

CodaFi
Copy link
Contributor

@CodaFi CodaFi commented Jul 5, 2018

This hack was only needed for Swift 3 mode in a narrow case. Flush it out of the compiler so we can simplify the space engine.

@CodaFi CodaFi requested a review from jrose-apple July 5, 2018 18:54
@CodaFi
Copy link
Contributor Author

CodaFi commented Jul 5, 2018

@swift-ci please smoke test

@CodaFi
Copy link
Contributor Author

CodaFi commented Jul 5, 2018

@swift-ci please test source compatibility

@davidungar
Copy link
Contributor

Good stuff!

@CodaFi
Copy link
Contributor Author

CodaFi commented Jul 5, 2018

Please test with following pull request:
swiftlang/swift-corelibs-libdispatch#381

@swift-ci Please smoke test Linux platform

Copy link
Contributor

@jrose-apple jrose-apple left a comment

Choose a reason for hiding this comment

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

Looks good! Only small comments, not relevant to the main diff.

SIMPLE_DECL_ATTR(_downgrade_exhaustivity_check, DowngradeExhaustivityCheck,
OnEnumElement |
LongAttribute | UserInaccessible,
71)
Copy link
Contributor

Choose a reason for hiding this comment

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

Can you leave behind a "71 is unused comment" here, like we did for other enums?

Technically this should probably mean bumping the module version too

@@ -1812,8 +1812,7 @@ CaseBlocks::CaseBlocks(
SGF.F.getResilienceExpansion());
}
if (canAssumeExhaustive) {
// Check that Sema didn't let any cases slip through. (This can happen
// with @_downgrade_exhaustivity_check.)
// Check that Sema didn't let any cases slip through.
Copy link
Contributor

Choose a reason for hiding this comment

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

I think this can't happen anymore, so maybe we can make this an assertion instead.

@CodaFi CodaFi force-pushed the irreconcilable-spatial-differences branch from 0bd059e to 6a93094 Compare July 5, 2018 22:14
This hack was only needed for Swift 3 mode in a narrow case.  Flush it out of the compiler so we can simplify the space engine.
@CodaFi CodaFi force-pushed the irreconcilable-spatial-differences branch from 6a93094 to 2fb5afb Compare August 24, 2018 18:00
@CodaFi
Copy link
Contributor Author

CodaFi commented Aug 24, 2018

Lost the original source compat failure. Let's try again

@swift-ci please test source compatibility

@CodaFi
Copy link
Contributor Author

CodaFi commented Aug 24, 2018

Please test with following pull request:
swiftlang/swift-corelibs-libdispatch#381

@swift-ci Please smoke test

@CodaFi
Copy link
Contributor Author

CodaFi commented Aug 24, 2018

Please test with following pull request:
swiftlang/swift-corelibs-libdispatch#381

@swift-ci Please smoke test Linux platform

@CodaFi
Copy link
Contributor Author

CodaFi commented Aug 24, 2018

⛵️

@CodaFi CodaFi merged commit 832307c into swiftlang:master Aug 24, 2018
@CodaFi CodaFi deleted the irreconcilable-spatial-differences branch August 24, 2018 21:00
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.

3 participants