-
Notifications
You must be signed in to change notification settings - Fork 207
Comment out @testable
and @_spi
#394
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
Conversation
@swift-ci please test |
This is much less than I thought. |
Great thought! Trying this at swiftlang/swift#35000 |
2055318
to
ac3c883
Compare
@swift-ci please test |
@artemcm Looks like swiftlang/swift#35000 passed. Does this PR merit approval? |
@swift-ci please test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In hindsight, I probably shouldn't have started introducing @_spi
into the codebase so early. This LGTM, and it should be easy to improve on once the feature is more stable
@@ -12,7 +12,7 @@ | |||
import XCTest | |||
import TSCBasic | |||
|
|||
@testable import SwiftDriver | |||
/*@testable*/ import SwiftDriver |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: We can probably drop the @testable
comments, I think we're better off never bringing them back assuming we can eventually start using @_spi
again.
Thanks, @owenv ! |
@swift-ci please test |
For now, comment out testable and _spi, which makes it easier to try the driver out with various versions of the compiler.
Someday, we can either uncomment the @SPI's, or we can move components into sub-modules. What do you think?