Per additional discussion and feedback in apple/swift-nio#1508, we're removing the message parameter from the precondition assertion methods entirely. Added a couple of missing @inlinables to match the declarations now present over there as well. (#85)
This commit is contained in:
parent
fe7e340f41
commit
4eb9bebfb8
|
|
@ -160,16 +160,13 @@ internal class NIOTSEventLoop: QoSEventLoop {
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
|
|
||||||
public func preconditionInEventLoop(_ message: @autoclosure() -> String, file: StaticString, line: UInt) {
|
@inlinable
|
||||||
/// `dispatchPrecondition(condition:)` is unable to accept an error message for the failure case, and we
|
public func preconditionInEventLoop(file: StaticString, line: UInt) {
|
||||||
/// can not safely rely on `self.inEventLoop` in this implementation. Any message provided by the caller
|
|
||||||
/// must therefore be ignored. We do not foresee ever being able to fix this behavior, given the design
|
|
||||||
/// constraints of the respective subsystems.
|
|
||||||
dispatchPrecondition(condition: .onQueue(self.loop))
|
dispatchPrecondition(condition: .onQueue(self.loop))
|
||||||
}
|
}
|
||||||
|
|
||||||
public func preconditionNotInEventLoop(_ message: @autoclosure() -> String = "", file: StaticString, line: UInt) {
|
@inlinable
|
||||||
/// As in our counterpart method, we can't do anything with the `message` parameter. See above for details.
|
public func preconditionNotInEventLoop(file: StaticString, line: UInt) {
|
||||||
dispatchPrecondition(condition: .notOnQueue(self.loop))
|
dispatchPrecondition(condition: .notOnQueue(self.loop))
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue