-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Add SPI for sources and observers to RunLoop #2807
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
These are for XCTest use only for now.
- Members should match the publicness/openness of their containers - Add a warning to getCFRunLoop() to warn porters that it's not going to be around forever.
@swift-ci please test |
Sources/Foundation/RunLoop.swift
Outdated
} | ||
|
||
@available(*, deprecated, message: "For XCTest use only.") | ||
open func remove(_ source: _Source, for mode: RunLoop.Mode) { |
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.
This should be underscored. A moment.
@swift-ci please test |
@swift-ci please test |
Sources/Foundation/RunLoop.swift
Outdated
let me = Unmanaged<_Source>.fromOpaque(info!).takeUnretainedValue() | ||
return .passRetained(String(describing: me)._cfObject) | ||
}, | ||
equal: { (infoA, infoB) -> DarwinBoolean in |
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.
The DarwinBoolean
is not portable, can we not use the DarwinBoolean
-> Bool
bridging here?
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.
This is a case where the types are different between platforms and I just need to drop the return value there, I think.
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.
File this under: why we want to stop exposing CF.
@swift-ci please test |
The module cache strikes again. |
@swift-ci please test |
Windows Run: https://dev.azure.com/compnerd/swift-build/_build/results?buildId=32451&view=results (looks good!) |
s-p-m flakeyness :-( |
|
@swift-ci please test Linux platform |
These are for XCTest use only for now. This is to support appropriate changes to swiftlang/swift-corelibs-xctest#304.