Swift Package IndexBuild Information
Successful build of Telegrammer, reference 1.0.0-alpha.4.0.1 (cc49bf), with Swift 6.1 for Linux on 25 Apr 2025 17:39:00 UTC.
Swift 6 data race errors: 36
Build Command
bash -c docker run --pull=always --rm -v "checkouts-4606859-0":/host -w "$PWD" registry.gitlab.com/finestructure/spi-images:basic-6.1-latest swift build --triple x86_64-unknown-linux-gnu 2>&1Build Log
51 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+stopPoll.swift:44:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
42 | */
43 | @discardableResult
44 | func stopPoll(params: StopPollParams) throws -> Future<Poll> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
45 | let body = try httpBody(for: params)
46 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+unbanChatMember.swift:39:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
37 | */
38 | @discardableResult
39 | func unbanChatMember(params: UnbanChatMemberParams) throws -> Future<Bool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
40 | let body = try httpBody(for: params)
41 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+unpinChatMessage.swift:34:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
32 | */
33 | @discardableResult
34 | func unpinChatMessage(params: UnpinChatMessageParams) throws -> Future<Bool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
35 | let body = try httpBody(for: params)
36 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+uploadStickerFile.swift:39:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
37 | */
38 | @discardableResult
39 | func uploadStickerFile(params: UploadStickerFileParams) throws -> Future<File> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
40 | let body = try httpBody(for: params)
41 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
[696/793] Compiling Telegrammer Dice.swift
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+stopMessageLiveLocation.swift:49:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
47 | */
48 | @discardableResult
49 | func stopMessageLiveLocation(params: StopMessageLiveLocationParams? = nil) throws -> Future<MessageOrBool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
50 | let body = try httpBody(for: params)
51 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+stopPoll.swift:44:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
42 | */
43 | @discardableResult
44 | func stopPoll(params: StopPollParams) throws -> Future<Poll> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
45 | let body = try httpBody(for: params)
46 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+unbanChatMember.swift:39:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
37 | */
38 | @discardableResult
39 | func unbanChatMember(params: UnbanChatMemberParams) throws -> Future<Bool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
40 | let body = try httpBody(for: params)
41 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+unpinChatMessage.swift:34:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
32 | */
33 | @discardableResult
34 | func unpinChatMessage(params: UnpinChatMessageParams) throws -> Future<Bool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
35 | let body = try httpBody(for: params)
36 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+uploadStickerFile.swift:39:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
37 | */
38 | @discardableResult
39 | func uploadStickerFile(params: UploadStickerFileParams) throws -> Future<File> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
40 | let body = try httpBody(for: params)
41 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
[697/793] Compiling Telegrammer Document.swift
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+stopMessageLiveLocation.swift:49:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
47 | */
48 | @discardableResult
49 | func stopMessageLiveLocation(params: StopMessageLiveLocationParams? = nil) throws -> Future<MessageOrBool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
50 | let body = try httpBody(for: params)
51 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+stopPoll.swift:44:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
42 | */
43 | @discardableResult
44 | func stopPoll(params: StopPollParams) throws -> Future<Poll> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
45 | let body = try httpBody(for: params)
46 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+unbanChatMember.swift:39:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
37 | */
38 | @discardableResult
39 | func unbanChatMember(params: UnbanChatMemberParams) throws -> Future<Bool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
40 | let body = try httpBody(for: params)
41 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+unpinChatMessage.swift:34:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
32 | */
33 | @discardableResult
34 | func unpinChatMessage(params: UnpinChatMessageParams) throws -> Future<Bool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
35 | let body = try httpBody(for: params)
36 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+uploadStickerFile.swift:39:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
37 | */
38 | @discardableResult
39 | func uploadStickerFile(params: UploadStickerFileParams) throws -> Future<File> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
40 | let body = try httpBody(for: params)
41 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
[698/793] Compiling Telegrammer EncryptedCredentials.swift
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+stopMessageLiveLocation.swift:49:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
47 | */
48 | @discardableResult
49 | func stopMessageLiveLocation(params: StopMessageLiveLocationParams? = nil) throws -> Future<MessageOrBool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
50 | let body = try httpBody(for: params)
51 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+stopPoll.swift:44:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
42 | */
43 | @discardableResult
44 | func stopPoll(params: StopPollParams) throws -> Future<Poll> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
45 | let body = try httpBody(for: params)
46 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+unbanChatMember.swift:39:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
37 | */
38 | @discardableResult
39 | func unbanChatMember(params: UnbanChatMemberParams) throws -> Future<Bool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
40 | let body = try httpBody(for: params)
41 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+unpinChatMessage.swift:34:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
32 | */
33 | @discardableResult
34 | func unpinChatMessage(params: UnpinChatMessageParams) throws -> Future<Bool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
35 | let body = try httpBody(for: params)
36 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+uploadStickerFile.swift:39:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
37 | */
38 | @discardableResult
39 | func uploadStickerFile(params: UploadStickerFileParams) throws -> Future<File> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
40 | let body = try httpBody(for: params)
41 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
[699/793] Compiling Telegrammer EncryptedPassportElement.swift
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+stopMessageLiveLocation.swift:49:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
47 | */
48 | @discardableResult
49 | func stopMessageLiveLocation(params: StopMessageLiveLocationParams? = nil) throws -> Future<MessageOrBool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
50 | let body = try httpBody(for: params)
51 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+stopPoll.swift:44:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
42 | */
43 | @discardableResult
44 | func stopPoll(params: StopPollParams) throws -> Future<Poll> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
45 | let body = try httpBody(for: params)
46 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+unbanChatMember.swift:39:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
37 | */
38 | @discardableResult
39 | func unbanChatMember(params: UnbanChatMemberParams) throws -> Future<Bool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
40 | let body = try httpBody(for: params)
41 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+unpinChatMessage.swift:34:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
32 | */
33 | @discardableResult
34 | func unpinChatMessage(params: UnpinChatMessageParams) throws -> Future<Bool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
35 | let body = try httpBody(for: params)
36 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+uploadStickerFile.swift:39:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
37 | */
38 | @discardableResult
39 | func uploadStickerFile(params: UploadStickerFileParams) throws -> Future<File> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
40 | let body = try httpBody(for: params)
41 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
[700/793] Compiling Telegrammer File.swift
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+stopMessageLiveLocation.swift:49:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
47 | */
48 | @discardableResult
49 | func stopMessageLiveLocation(params: StopMessageLiveLocationParams? = nil) throws -> Future<MessageOrBool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
50 | let body = try httpBody(for: params)
51 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+stopPoll.swift:44:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
42 | */
43 | @discardableResult
44 | func stopPoll(params: StopPollParams) throws -> Future<Poll> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
45 | let body = try httpBody(for: params)
46 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+unbanChatMember.swift:39:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
37 | */
38 | @discardableResult
39 | func unbanChatMember(params: UnbanChatMemberParams) throws -> Future<Bool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
40 | let body = try httpBody(for: params)
41 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+unpinChatMessage.swift:34:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
32 | */
33 | @discardableResult
34 | func unpinChatMessage(params: UnpinChatMessageParams) throws -> Future<Bool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
35 | let body = try httpBody(for: params)
36 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+uploadStickerFile.swift:39:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
37 | */
38 | @discardableResult
39 | func uploadStickerFile(params: UploadStickerFileParams) throws -> Future<File> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
40 | let body = try httpBody(for: params)
41 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
[701/793] Compiling Telegrammer ForceReply.swift
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+stopMessageLiveLocation.swift:49:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
47 | */
48 | @discardableResult
49 | func stopMessageLiveLocation(params: StopMessageLiveLocationParams? = nil) throws -> Future<MessageOrBool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
50 | let body = try httpBody(for: params)
51 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+stopPoll.swift:44:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
42 | */
43 | @discardableResult
44 | func stopPoll(params: StopPollParams) throws -> Future<Poll> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
45 | let body = try httpBody(for: params)
46 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+unbanChatMember.swift:39:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
37 | */
38 | @discardableResult
39 | func unbanChatMember(params: UnbanChatMemberParams) throws -> Future<Bool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
40 | let body = try httpBody(for: params)
41 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+unpinChatMessage.swift:34:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
32 | */
33 | @discardableResult
34 | func unpinChatMessage(params: UnpinChatMessageParams) throws -> Future<Bool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
35 | let body = try httpBody(for: params)
36 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+uploadStickerFile.swift:39:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
37 | */
38 | @discardableResult
39 | func uploadStickerFile(params: UploadStickerFileParams) throws -> Future<File> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
40 | let body = try httpBody(for: params)
41 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
[702/793] Compiling Telegrammer Game.swift
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+stopMessageLiveLocation.swift:49:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
47 | */
48 | @discardableResult
49 | func stopMessageLiveLocation(params: StopMessageLiveLocationParams? = nil) throws -> Future<MessageOrBool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
50 | let body = try httpBody(for: params)
51 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+stopPoll.swift:44:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
42 | */
43 | @discardableResult
44 | func stopPoll(params: StopPollParams) throws -> Future<Poll> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
45 | let body = try httpBody(for: params)
46 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+unbanChatMember.swift:39:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
37 | */
38 | @discardableResult
39 | func unbanChatMember(params: UnbanChatMemberParams) throws -> Future<Bool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
40 | let body = try httpBody(for: params)
41 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+unpinChatMessage.swift:34:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
32 | */
33 | @discardableResult
34 | func unpinChatMessage(params: UnpinChatMessageParams) throws -> Future<Bool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
35 | let body = try httpBody(for: params)
36 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+uploadStickerFile.swift:39:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
37 | */
38 | @discardableResult
39 | func uploadStickerFile(params: UploadStickerFileParams) throws -> Future<File> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
40 | let body = try httpBody(for: params)
41 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
[703/793] Compiling Telegrammer GameHighScore.swift
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+stopMessageLiveLocation.swift:49:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
47 | */
48 | @discardableResult
49 | func stopMessageLiveLocation(params: StopMessageLiveLocationParams? = nil) throws -> Future<MessageOrBool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
50 | let body = try httpBody(for: params)
51 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+stopPoll.swift:44:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
42 | */
43 | @discardableResult
44 | func stopPoll(params: StopPollParams) throws -> Future<Poll> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
45 | let body = try httpBody(for: params)
46 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+unbanChatMember.swift:39:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
37 | */
38 | @discardableResult
39 | func unbanChatMember(params: UnbanChatMemberParams) throws -> Future<Bool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
40 | let body = try httpBody(for: params)
41 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+unpinChatMessage.swift:34:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
32 | */
33 | @discardableResult
34 | func unpinChatMessage(params: UnpinChatMessageParams) throws -> Future<Bool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
35 | let body = try httpBody(for: params)
36 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+uploadStickerFile.swift:39:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
37 | */
38 | @discardableResult
39 | func uploadStickerFile(params: UploadStickerFileParams) throws -> Future<File> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
40 | let body = try httpBody(for: params)
41 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
[704/793] Compiling Telegrammer InlineKeyboardButton.swift
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+stopMessageLiveLocation.swift:49:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
47 | */
48 | @discardableResult
49 | func stopMessageLiveLocation(params: StopMessageLiveLocationParams? = nil) throws -> Future<MessageOrBool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
50 | let body = try httpBody(for: params)
51 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+stopPoll.swift:44:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
42 | */
43 | @discardableResult
44 | func stopPoll(params: StopPollParams) throws -> Future<Poll> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
45 | let body = try httpBody(for: params)
46 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+unbanChatMember.swift:39:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
37 | */
38 | @discardableResult
39 | func unbanChatMember(params: UnbanChatMemberParams) throws -> Future<Bool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
40 | let body = try httpBody(for: params)
41 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+unpinChatMessage.swift:34:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
32 | */
33 | @discardableResult
34 | func unpinChatMessage(params: UnpinChatMessageParams) throws -> Future<Bool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
35 | let body = try httpBody(for: params)
36 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+uploadStickerFile.swift:39:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
37 | */
38 | @discardableResult
39 | func uploadStickerFile(params: UploadStickerFileParams) throws -> Future<File> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
40 | let body = try httpBody(for: params)
41 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
[705/793] Emitting module Telegrammer
/host/spi-builder-workspace/Sources/Telegrammer/Bot/BotProtocol.swift:8:30: warning: using 'class' keyword to define a class-constrained protocol is deprecated; use 'AnyObject' instead
6 | //
7 |
8 | public protocol BotProtocol: class {}
| `- warning: using 'class' keyword to define a class-constrained protocol is deprecated; use 'AnyObject' instead
9 |
10 | public protocol AutoMockable {}
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Jobs/BasicJobQueue.swift:14:12: warning: extraneous whitespace between attribute name and '('; this is an error in the Swift 6 language mode
12 | public class BasicJobQueue<C>: JobQueue {
13 |
14 | private (set) var bot: BotProtocol
| `- warning: extraneous whitespace between attribute name and '('; this is an error in the Swift 6 language mode
15 | private (set) var worker: Worker
16 |
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Jobs/BasicJobQueue.swift:15:12: warning: extraneous whitespace between attribute name and '('; this is an error in the Swift 6 language mode
13 |
14 | private (set) var bot: BotProtocol
15 | private (set) var worker: Worker
| `- warning: extraneous whitespace between attribute name and '('; this is an error in the Swift 6 language mode
16 |
17 | public var jobs = SynchronizedArray<AnyJob<C>>()
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+addStickerToSet.swift:59:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
57 | */
58 | @discardableResult
59 | func addStickerToSet(params: AddStickerToSetParams) throws -> Future<Bool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
60 | let body = try httpBody(for: params)
61 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+answerCallbackQuery.swift:57:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
55 | */
56 | @discardableResult
57 | func answerCallbackQuery(params: AnswerCallbackQueryParams) throws -> Future<Bool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
58 | let body = try httpBody(for: params)
59 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+answerInlineQuery.swift:67:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
65 | */
66 | @discardableResult
67 | func answerInlineQuery(params: AnswerInlineQueryParams) throws -> Future<Bool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
68 | let body = try httpBody(for: params)
69 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+answerPreCheckoutQuery.swift:44:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
42 | */
43 | @discardableResult
44 | func answerPreCheckoutQuery(params: AnswerPreCheckoutQueryParams) throws -> Future<Bool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
45 | let body = try httpBody(for: params)
46 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+answerShippingQuery.swift:49:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
47 | */
48 | @discardableResult
49 | func answerShippingQuery(params: AnswerShippingQueryParams) throws -> Future<Bool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
50 | let body = try httpBody(for: params)
51 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+createNewStickerSet.swift:69:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
67 | */
68 | @discardableResult
69 | func createNewStickerSet(params: CreateNewStickerSetParams) throws -> Future<Bool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
70 | let body = try httpBody(for: params)
71 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+deleteChatPhoto.swift:34:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
32 | */
33 | @discardableResult
34 | func deleteChatPhoto(params: DeleteChatPhotoParams) throws -> Future<Bool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
35 | let body = try httpBody(for: params)
36 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+deleteChatStickerSet.swift:34:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
32 | */
33 | @discardableResult
34 | func deleteChatStickerSet(params: DeleteChatStickerSetParams) throws -> Future<Bool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
35 | let body = try httpBody(for: params)
36 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+deleteMessage.swift:47:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
45 | */
46 | @discardableResult
47 | func deleteMessage(params: DeleteMessageParams) throws -> Future<Bool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
48 | let body = try httpBody(for: params)
49 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+deleteStickerFromSet.swift:34:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
32 | */
33 | @discardableResult
34 | func deleteStickerFromSet(params: DeleteStickerFromSetParams) throws -> Future<Bool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
35 | let body = try httpBody(for: params)
36 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+deleteWebhook.swift:18:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
16 | */
17 | @discardableResult
18 | func deleteWebhook() throws -> Future<Bool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
19 | return try client
20 | .request(endpoint: "deleteWebhook")
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+editMessageCaption.swift:59:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
57 | */
58 | @discardableResult
59 | func editMessageCaption(params: EditMessageCaptionParams? = nil) throws -> Future<MessageOrBool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
60 | let body = try httpBody(for: params)
61 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+editMessageLiveLocation.swift:59:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
57 | */
58 | @discardableResult
59 | func editMessageLiveLocation(params: EditMessageLiveLocationParams) throws -> Future<MessageOrBool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
60 | let body = try httpBody(for: params)
61 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+editMessageMedia.swift:54:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
52 | */
53 | @discardableResult
54 | func editMessageMedia(params: EditMessageMediaParams) throws -> Future<MessageOrBool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
55 | let body = try httpBody(for: params)
56 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+editMessageReplyMarkup.swift:49:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
47 | */
48 | @discardableResult
49 | func editMessageReplyMarkup(params: EditMessageReplyMarkupParams? = nil) throws -> Future<MessageOrBool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
50 | let body = try httpBody(for: params)
51 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+editMessageText.swift:64:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
62 | */
63 | @discardableResult
64 | func editMessageText(params: EditMessageTextParams) throws -> Future<MessageOrBool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
65 | let body = try httpBody(for: params)
66 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+exportChatInviteLink.swift:34:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
32 | */
33 | @discardableResult
34 | func exportChatInviteLink(params: ExportChatInviteLinkParams) throws -> Future<String> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
35 | let body = try httpBody(for: params)
36 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+forwardMessage.swift:49:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
47 | */
48 | @discardableResult
49 | func forwardMessage(params: ForwardMessageParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
50 | let body = try httpBody(for: params)
51 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+getChat.swift:34:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
32 | */
33 | @discardableResult
34 | func getChat(params: GetChatParams) throws -> Future<Chat> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
35 | let body = try httpBody(for: params)
36 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+getChatAdministrators.swift:34:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
32 | */
33 | @discardableResult
34 | func getChatAdministrators(params: GetChatAdministratorsParams) throws -> Future<[ChatMember]> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
35 | let body = try httpBody(for: params)
36 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+getChatMember.swift:39:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
37 | */
38 | @discardableResult
39 | func getChatMember(params: GetChatMemberParams) throws -> Future<ChatMember> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
40 | let body = try httpBody(for: params)
41 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+getChatMembersCount.swift:34:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
32 | */
33 | @discardableResult
34 | func getChatMembersCount(params: GetChatMembersCountParams) throws -> Future<Int> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
35 | let body = try httpBody(for: params)
36 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+getFile.swift:34:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
32 | */
33 | @discardableResult
34 | func getFile(params: GetFileParams) throws -> Future<File> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
35 | let body = try httpBody(for: params)
36 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+getGameHighScores.swift:50:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
48 | */
49 | @discardableResult
50 | func getGameHighScores(params: GetGameHighScoresParams) throws -> Future<[GameHighScore]> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
51 | let body = try httpBody(for: params)
52 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+getMe.swift:18:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
16 | */
17 | @discardableResult
18 | func getMe() throws -> Future<User> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
19 | return try client
20 | .request(endpoint: "getMe")
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+getMyCommands.swift:18:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
16 | */
17 | @discardableResult
18 | func getMyCommands() throws -> Future<[BotCommand]> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
19 | return try client
20 | .request(endpoint: "getMyCommands")
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+getStickerSet.swift:34:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
32 | */
33 | @discardableResult
34 | func getStickerSet(params: GetStickerSetParams) throws -> Future<StickerSet> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
35 | let body = try httpBody(for: params)
36 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+getUpdates.swift:51:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
49 | */
50 | @discardableResult
51 | func getUpdates(params: GetUpdatesParams? = nil) throws -> Future<[Update]> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
52 | let body = try httpBody(for: params)
53 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+getUserProfilePhotos.swift:44:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
42 | */
43 | @discardableResult
44 | func getUserProfilePhotos(params: GetUserProfilePhotosParams) throws -> Future<UserProfilePhotos> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
45 | let body = try httpBody(for: params)
46 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+getWebhookInfo.swift:18:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
16 | */
17 | @discardableResult
18 | func getWebhookInfo() throws -> Future<WebhookInfo> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
19 | return try client
20 | .request(endpoint: "getWebhookInfo")
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+kickChatMember.swift:44:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
42 | */
43 | @discardableResult
44 | func kickChatMember(params: KickChatMemberParams) throws -> Future<Bool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
45 | let body = try httpBody(for: params)
46 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+leaveChat.swift:34:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
32 | */
33 | @discardableResult
34 | func leaveChat(params: LeaveChatParams) throws -> Future<Bool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
35 | let body = try httpBody(for: params)
36 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+pinChatMessage.swift:44:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
42 | */
43 | @discardableResult
44 | func pinChatMessage(params: PinChatMessageParams) throws -> Future<Bool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
45 | let body = try httpBody(for: params)
46 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+promoteChatMember.swift:79:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
77 | */
78 | @discardableResult
79 | func promoteChatMember(params: PromoteChatMemberParams) throws -> Future<Bool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
80 | let body = try httpBody(for: params)
81 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+restrictChatMember.swift:49:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
47 | */
48 | @discardableResult
49 | func restrictChatMember(params: RestrictChatMemberParams) throws -> Future<Bool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
50 | let body = try httpBody(for: params)
51 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendAnimation.swift:84:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
82 | */
83 | @discardableResult
84 | func sendAnimation(params: SendAnimationParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
85 | let body = try httpBody(for: params)
86 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendAudio.swift:85:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
83 | */
84 | @discardableResult
85 | func sendAudio(params: SendAudioParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
86 | let body = try httpBody(for: params)
87 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendChatAction.swift:41:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
39 | */
40 | @discardableResult
41 | func sendChatAction(params: SendChatActionParams) throws -> Future<Bool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
42 | let body = try httpBody(for: params)
43 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendContact.swift:69:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
67 | */
68 | @discardableResult
69 | func sendContact(params: SendContactParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
70 | let body = try httpBody(for: params)
71 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendDice.swift:54:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
52 | */
53 | @discardableResult
54 | func sendDice(params: SendDiceParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
55 | let body = try httpBody(for: params)
56 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendDocument.swift:69:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
67 | */
68 | @discardableResult
69 | func sendDocument(params: SendDocumentParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
70 | let body = try httpBody(for: params)
71 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendGame.swift:54:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
52 | */
53 | @discardableResult
54 | func sendGame(params: SendGameParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
55 | let body = try httpBody(for: params)
56 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendInvoice.swift:144:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
142 | */
143 | @discardableResult
144 | func sendInvoice(params: SendInvoiceParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
145 | let body = try httpBody(for: params)
146 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendLocation.swift:64:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
62 | */
63 | @discardableResult
64 | func sendLocation(params: SendLocationParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
65 | let body = try httpBody(for: params)
66 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendMediaGroup.swift:49:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
47 | */
48 | @discardableResult
49 | func sendMediaGroup(params: SendMediaGroupParams) throws -> Future<[Message]> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
50 | let body = try httpBody(for: params)
51 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendMessage.swift:64:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
62 | */
63 | @discardableResult
64 | func sendMessage(params: SendMessageParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
65 | let body = try httpBody(for: params)
66 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendPhoto.swift:64:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
62 | */
63 | @discardableResult
64 | func sendPhoto(params: SendPhotoParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
65 | let body = try httpBody(for: params)
66 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendPoll.swift:104:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
102 | */
103 | @discardableResult
104 | func sendPoll(params: SendPollParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
105 | let body = try httpBody(for: params)
106 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendSticker.swift:54:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
52 | */
53 | @discardableResult
54 | func sendSticker(params: SendStickerParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
55 | let body = try httpBody(for: params)
56 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendVenue.swift:79:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
77 | */
78 | @discardableResult
79 | func sendVenue(params: SendVenueParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
80 | let body = try httpBody(for: params)
81 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendVideo.swift:89:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
87 | */
88 | @discardableResult
89 | func sendVideo(params: SendVideoParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
90 | let body = try httpBody(for: params)
91 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendVideoNote.swift:69:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
67 | */
68 | @discardableResult
69 | func sendVideoNote(params: SendVideoNoteParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
70 | let body = try httpBody(for: params)
71 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendVoice.swift:69:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
67 | */
68 | @discardableResult
69 | func sendVoice(params: SendVoiceParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
70 | let body = try httpBody(for: params)
71 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+setChatAdministratorCustomTitle.swift:44:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
42 | */
43 | @discardableResult
44 | func setChatAdministratorCustomTitle(params: SetChatAdministratorCustomTitleParams) throws -> Future<Bool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
45 | let body = try httpBody(for: params)
46 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+setChatDescription.swift:39:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
37 | */
38 | @discardableResult
39 | func setChatDescription(params: SetChatDescriptionParams) throws -> Future<Bool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
40 | let body = try httpBody(for: params)
41 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+setChatPermissions.swift:39:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
37 | */
38 | @discardableResult
39 | func setChatPermissions(params: SetChatPermissionsParams) throws -> Future<Bool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
40 | let body = try httpBody(for: params)
41 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+setChatPhoto.swift:39:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
37 | */
38 | @discardableResult
39 | func setChatPhoto(params: SetChatPhotoParams) throws -> Future<Bool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
40 | let body = try httpBody(for: params)
41 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+setChatStickerSet.swift:39:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
37 | */
38 | @discardableResult
39 | func setChatStickerSet(params: SetChatStickerSetParams) throws -> Future<Bool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
40 | let body = try httpBody(for: params)
41 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+setChatTitle.swift:39:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
37 | */
38 | @discardableResult
39 | func setChatTitle(params: SetChatTitleParams) throws -> Future<Bool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
40 | let body = try httpBody(for: params)
41 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+setGameScore.swift:64:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
62 | */
63 | @discardableResult
64 | func setGameScore(params: SetGameScoreParams) throws -> Future<Bool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
65 | let body = try httpBody(for: params)
66 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+setMyCommands.swift:34:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
32 | */
33 | @discardableResult
34 | func setMyCommands(params: SetMyCommandsParams) throws -> Future<Bool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
35 | let body = try httpBody(for: params)
36 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+setPassportDataErrors.swift:40:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
38 | */
39 | @discardableResult
40 | func setPassportDataErrors(params: SetPassportDataErrorsParams) throws -> Future<Bool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
41 | let body = try httpBody(for: params)
42 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+setStickerPositionInSet.swift:39:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
37 | */
38 | @discardableResult
39 | func setStickerPositionInSet(params: SetStickerPositionInSetParams) throws -> Future<Bool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
40 | let body = try httpBody(for: params)
41 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+setStickerSetThumb.swift:44:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
42 | */
43 | @discardableResult
44 | func setStickerSetThumb(params: SetStickerSetThumbParams) throws -> Future<Bool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
45 | let body = try httpBody(for: params)
46 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+setWebhook.swift:52:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
50 | */
51 | @discardableResult
52 | func setWebhook(params: SetWebhookParams) throws -> Future<Bool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
53 | let body = try httpBody(for: params)
54 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+stopMessageLiveLocation.swift:49:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
47 | */
48 | @discardableResult
49 | func stopMessageLiveLocation(params: StopMessageLiveLocationParams? = nil) throws -> Future<MessageOrBool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
50 | let body = try httpBody(for: params)
51 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+stopPoll.swift:44:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
42 | */
43 | @discardableResult
44 | func stopPoll(params: StopPollParams) throws -> Future<Poll> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
45 | let body = try httpBody(for: params)
46 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+unbanChatMember.swift:39:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
37 | */
38 | @discardableResult
39 | func unbanChatMember(params: UnbanChatMemberParams) throws -> Future<Bool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
40 | let body = try httpBody(for: params)
41 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+unpinChatMessage.swift:34:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
32 | */
33 | @discardableResult
34 | func unpinChatMessage(params: UnpinChatMessageParams) throws -> Future<Bool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
35 | let body = try httpBody(for: params)
36 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
/host/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+uploadStickerFile.swift:39:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
37 | */
38 | @discardableResult
39 | func uploadStickerFile(params: UploadStickerFileParams) throws -> Future<File> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
40 | let body = try httpBody(for: params)
41 | let headers = httpHeaders(for: params)
/host/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
406 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
407 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
408 | @usableFromInline
[706/793] Compiling Telegrammer RegexpFilter.swift
[707/793] Compiling Telegrammer ReplyFilter.swift
[708/793] Compiling Telegrammer StatusUpdateFilters.swift
[709/793] Compiling Telegrammer StickerFilter.swift
[710/793] Compiling Telegrammer SuccesfulPaymentFilter.swift
[711/793] Compiling Telegrammer TextFilter.swift
[712/793] Compiling Telegrammer UserFilter.swift
[713/793] Compiling Telegrammer VenueFilter.swift
[714/793] Compiling Telegrammer VideoFilter.swift
[715/793] Compiling Telegrammer VideoNoteFilter.swift
[716/793] Compiling Telegrammer VoiceFilter.swift
[717/793] Compiling Telegrammer CallbackQueryHandler.swift
[718/793] Compiling Telegrammer CommandHandler.swift
[719/793] Compiling Telegrammer ConversationHandler.swift
[720/793] Compiling Telegrammer Handler.swift
[721/793] Compiling Telegrammer LoggerHandler.swift
[722/793] Compiling Telegrammer MessageHandler.swift
[723/793] Compiling Telegrammer RegexpHandler.swift
[724/793] Compiling Telegrammer Constants.swift
[725/793] Compiling Telegrammer Enviroment+Helper.swift
[726/793] Compiling Telegrammer Error+Helpers.swift
[727/793] Compiling Telegrammer HTTPHeader+Helper.swift
[728/793] Compiling Telegrammer HTTPRequest+Helper.swift
[729/793] Compiling Telegrammer MultipartPartConvertible+Helper.swift
[730/793] Compiling Telegrammer Voice.swift
[731/793] Compiling Telegrammer WebhookInfo.swift
[732/793] Compiling Telegrammer Storage.swift
[733/793] Compiling Telegrammer Dispatcher.swift
[734/793] Compiling Telegrammer HandlerGroup.swift
[735/793] Compiling Telegrammer HandlersQueue.swift
[736/793] Compiling Telegrammer BotError.swift
[737/793] Compiling Telegrammer AllFilter.swift
[738/793] Compiling Telegrammer AudioFilter.swift
[739/793] Compiling Telegrammer CaptionEntityFilter.swift
[740/793] Compiling Telegrammer ChatFilter.swift
[741/793] Compiling Telegrammer CommandFilter.swift
[742/793] Compiling Telegrammer ContactFilter.swift
[743/793] Compiling Telegrammer DocumentFilter.swift
[744/793] Compiling Telegrammer EntityFilter.swift
[745/793] Compiling Telegrammer Filter.swift
[746/793] Compiling Telegrammer ForwarderFilter.swift
[747/793] Compiling Telegrammer GameFilter.swift
[748/793] Compiling Telegrammer GroupFilter.swift
[749/793] Compiling Telegrammer InvoiceFilter.swift
[750/793] Compiling Telegrammer LanguageFilter.swift
[751/793] Compiling Telegrammer LocationFilter.swift
[752/793] Compiling Telegrammer PhotoFilter.swift
[753/793] Compiling Telegrammer PrivateFilter.swift
[754/793] Compiling Telegrammer String+Helper.swift
/host/spi-builder-workspace/Sources/Telegrammer/Helpers/SynchronizedArray.swift:326:52: warning: reference to captured var 'elements' in concurrently-executing code; this is an error in the Swift 6 language mode
324 | }
325 |
326 | DispatchQueue.main.async { completion?(elements) }
| `- warning: reference to captured var 'elements' in concurrently-executing code; this is an error in the Swift 6 language mode
327 | }
328 | }
[755/793] Compiling Telegrammer SynchronizedArray.swift
/host/spi-builder-workspace/Sources/Telegrammer/Helpers/SynchronizedArray.swift:326:52: warning: reference to captured var 'elements' in concurrently-executing code; this is an error in the Swift 6 language mode
324 | }
325 |
326 | DispatchQueue.main.async { completion?(elements) }
| `- warning: reference to captured var 'elements' in concurrently-executing code; this is an error in the Swift 6 language mode
327 | }
328 | }
[756/793] Compiling Telegrammer TimeAmount+Helpers.swift
/host/spi-builder-workspace/Sources/Telegrammer/Helpers/SynchronizedArray.swift:326:52: warning: reference to captured var 'elements' in concurrently-executing code; this is an error in the Swift 6 language mode
324 | }
325 |
326 | DispatchQueue.main.async { completion?(elements) }
| `- warning: reference to captured var 'elements' in concurrently-executing code; this is an error in the Swift 6 language mode
327 | }
328 | }
[757/793] Compiling Telegrammer Bot.Settings+Proxy.swift
/host/spi-builder-workspace/Sources/Telegrammer/Helpers/SynchronizedArray.swift:326:52: warning: reference to captured var 'elements' in concurrently-executing code; this is an error in the Swift 6 language mode
324 | }
325 |
326 | DispatchQueue.main.async { completion?(elements) }
| `- warning: reference to captured var 'elements' in concurrently-executing code; this is an error in the Swift 6 language mode
327 | }
328 | }
[758/793] Compiling Telegrammer BotClient.swift
/host/spi-builder-workspace/Sources/Telegrammer/Helpers/SynchronizedArray.swift:326:52: warning: reference to captured var 'elements' in concurrently-executing code; this is an error in the Swift 6 language mode
324 | }
325 |
326 | DispatchQueue.main.async { completion?(elements) }
| `- warning: reference to captured var 'elements' in concurrently-executing code; this is an error in the Swift 6 language mode
327 | }
328 | }
[759/793] Compiling Telegrammer Longpolling.swift
/host/spi-builder-workspace/Sources/Telegrammer/Helpers/SynchronizedArray.swift:326:52: warning: reference to captured var 'elements' in concurrently-executing code; this is an error in the Swift 6 language mode
324 | }
325 |
326 | DispatchQueue.main.async { completion?(elements) }
| `- warning: reference to captured var 'elements' in concurrently-executing code; this is an error in the Swift 6 language mode
327 | }
328 | }
[760/793] Compiling Telegrammer Network.swift
/host/spi-builder-workspace/Sources/Telegrammer/Helpers/SynchronizedArray.swift:326:52: warning: reference to captured var 'elements' in concurrently-executing code; this is an error in the Swift 6 language mode
324 | }
325 |
326 | DispatchQueue.main.async { completion?(elements) }
| `- warning: reference to captured var 'elements' in concurrently-executing code; this is an error in the Swift 6 language mode
327 | }
328 | }
[761/793] Compiling Telegrammer UpdatesServer.swift
/host/spi-builder-workspace/Sources/Telegrammer/Helpers/SynchronizedArray.swift:326:52: warning: reference to captured var 'elements' in concurrently-executing code; this is an error in the Swift 6 language mode
324 | }
325 |
326 | DispatchQueue.main.async { completion?(elements) }
| `- warning: reference to captured var 'elements' in concurrently-executing code; this is an error in the Swift 6 language mode
327 | }
328 | }
[762/793] Compiling Telegrammer Webhooks.swift
/host/spi-builder-workspace/Sources/Telegrammer/Helpers/SynchronizedArray.swift:326:52: warning: reference to captured var 'elements' in concurrently-executing code; this is an error in the Swift 6 language mode
324 | }
325 |
326 | DispatchQueue.main.async { completion?(elements) }
| `- warning: reference to captured var 'elements' in concurrently-executing code; this is an error in the Swift 6 language mode
327 | }
328 | }
[763/793] Compiling Telegrammer ChatId.swift
/host/spi-builder-workspace/Sources/Telegrammer/Helpers/SynchronizedArray.swift:326:52: warning: reference to captured var 'elements' in concurrently-executing code; this is an error in the Swift 6 language mode
324 | }
325 |
326 | DispatchQueue.main.async { completion?(elements) }
| `- warning: reference to captured var 'elements' in concurrently-executing code; this is an error in the Swift 6 language mode
327 | }
328 | }
[764/793] Compiling Telegrammer ChatType.swift
/host/spi-builder-workspace/Sources/Telegrammer/Helpers/SynchronizedArray.swift:326:52: warning: reference to captured var 'elements' in concurrently-executing code; this is an error in the Swift 6 language mode
324 | }
325 |
326 | DispatchQueue.main.async { completion?(elements) }
| `- warning: reference to captured var 'elements' in concurrently-executing code; this is an error in the Swift 6 language mode
327 | }
328 | }
[765/793] Compiling Telegrammer FileInfo.swift
/host/spi-builder-workspace/Sources/Telegrammer/Helpers/SynchronizedArray.swift:326:52: warning: reference to captured var 'elements' in concurrently-executing code; this is an error in the Swift 6 language mode
324 | }
325 |
326 | DispatchQueue.main.async { completion?(elements) }
| `- warning: reference to captured var 'elements' in concurrently-executing code; this is an error in the Swift 6 language mode
327 | }
328 | }
[766/793] Compiling Telegrammer InlineQueryResult.swift
/host/spi-builder-workspace/Sources/Telegrammer/Helpers/SynchronizedArray.swift:326:52: warning: reference to captured var 'elements' in concurrently-executing code; this is an error in the Swift 6 language mode
324 | }
325 |
326 | DispatchQueue.main.async { completion?(elements) }
| `- warning: reference to captured var 'elements' in concurrently-executing code; this is an error in the Swift 6 language mode
327 | }
328 | }
[767/793] Compiling Telegrammer InputFile.swift
/host/spi-builder-workspace/Sources/Telegrammer/Helpers/SynchronizedArray.swift:326:52: warning: reference to captured var 'elements' in concurrently-executing code; this is an error in the Swift 6 language mode
324 | }
325 |
326 | DispatchQueue.main.async { completion?(elements) }
| `- warning: reference to captured var 'elements' in concurrently-executing code; this is an error in the Swift 6 language mode
327 | }
328 | }
[768/793] Compiling Telegrammer InputMedia.swift
/host/spi-builder-workspace/Sources/Telegrammer/Helpers/SynchronizedArray.swift:326:52: warning: reference to captured var 'elements' in concurrently-executing code; this is an error in the Swift 6 language mode
324 | }
325 |
326 | DispatchQueue.main.async { completion?(elements) }
| `- warning: reference to captured var 'elements' in concurrently-executing code; this is an error in the Swift 6 language mode
327 | }
328 | }
[769/793] Compiling Telegrammer InputMessageContent.swift
/host/spi-builder-workspace/Sources/Telegrammer/Helpers/SynchronizedArray.swift:326:52: warning: reference to captured var 'elements' in concurrently-executing code; this is an error in the Swift 6 language mode
324 | }
325 |
326 | DispatchQueue.main.async { completion?(elements) }
| `- warning: reference to captured var 'elements' in concurrently-executing code; this is an error in the Swift 6 language mode
327 | }
328 | }
[770/793] Compiling Telegrammer MessageEntityType.swift
/host/spi-builder-workspace/Sources/Telegrammer/Helpers/SynchronizedArray.swift:326:52: warning: reference to captured var 'elements' in concurrently-executing code; this is an error in the Swift 6 language mode
324 | }
325 |
326 | DispatchQueue.main.async { completion?(elements) }
| `- warning: reference to captured var 'elements' in concurrently-executing code; this is an error in the Swift 6 language mode
327 | }
328 | }
[771/793] Compiling Telegrammer MessageOrBool.swift
/host/spi-builder-workspace/Sources/Telegrammer/Helpers/SynchronizedArray.swift:326:52: warning: reference to captured var 'elements' in concurrently-executing code; this is an error in the Swift 6 language mode
324 | }
325 |
326 | DispatchQueue.main.async { completion?(elements) }
| `- warning: reference to captured var 'elements' in concurrently-executing code; this is an error in the Swift 6 language mode
327 | }
328 | }
[772/793] Compiling Telegrammer ParseMode.swift
/host/spi-builder-workspace/Sources/Telegrammer/Helpers/SynchronizedArray.swift:326:52: warning: reference to captured var 'elements' in concurrently-executing code; this is an error in the Swift 6 language mode
324 | }
325 |
326 | DispatchQueue.main.async { completion?(elements) }
| `- warning: reference to captured var 'elements' in concurrently-executing code; this is an error in the Swift 6 language mode
327 | }
328 | }
[773/793] Compiling Telegrammer PassportElementError.swift
/host/spi-builder-workspace/Sources/Telegrammer/Helpers/SynchronizedArray.swift:326:52: warning: reference to captured var 'elements' in concurrently-executing code; this is an error in the Swift 6 language mode
324 | }
325 |
326 | DispatchQueue.main.async { completion?(elements) }
| `- warning: reference to captured var 'elements' in concurrently-executing code; this is an error in the Swift 6 language mode
327 | }
328 | }
[774/793] Compiling Telegrammer ReplyMarkup.swift
/host/spi-builder-workspace/Sources/Telegrammer/Helpers/SynchronizedArray.swift:326:52: warning: reference to captured var 'elements' in concurrently-executing code; this is an error in the Swift 6 language mode
324 | }
325 |
326 | DispatchQueue.main.async { completion?(elements) }
| `- warning: reference to captured var 'elements' in concurrently-executing code; this is an error in the Swift 6 language mode
327 | }
328 | }
[775/793] Compiling Telegrammer TelegramContainer.swift
/host/spi-builder-workspace/Sources/Telegrammer/Helpers/SynchronizedArray.swift:326:52: warning: reference to captured var 'elements' in concurrently-executing code; this is an error in the Swift 6 language mode
324 | }
325 |
326 | DispatchQueue.main.async { completion?(elements) }
| `- warning: reference to captured var 'elements' in concurrently-executing code; this is an error in the Swift 6 language mode
327 | }
328 | }
[776/793] Compiling Telegrammer TelegramEncodables.swift
/host/spi-builder-workspace/Sources/Telegrammer/Helpers/SynchronizedArray.swift:326:52: warning: reference to captured var 'elements' in concurrently-executing code; this is an error in the Swift 6 language mode
324 | }
325 |
326 | DispatchQueue.main.async { completion?(elements) }
| `- warning: reference to captured var 'elements' in concurrently-executing code; this is an error in the Swift 6 language mode
327 | }
328 | }
[777/793] Compiling Telegrammer Updater.swift
/host/spi-builder-workspace/Sources/Telegrammer/Helpers/SynchronizedArray.swift:326:52: warning: reference to captured var 'elements' in concurrently-executing code; this is an error in the Swift 6 language mode
324 | }
325 |
326 | DispatchQueue.main.async { completion?(elements) }
| `- warning: reference to captured var 'elements' in concurrently-executing code; this is an error in the Swift 6 language mode
327 | }
328 | }
[779/807] Compiling DemoWebhooksLocally main.swift
[780/810] Emitting module DemoSchedulerBot
[781/810] Compiling DemoSchedulerBot main.swift
[782/810] Emitting module DemoWebhooksLocally
[783/811] Compiling DemoSpellCheckerBot Array+Helper.swift
[786/812] Compiling DemoSpellCheckerBot YaSpellCheck.swift
[787/812] Compiling DemoSpellCheckerBot YaSpellChecker.swift
/host/spi-builder-workspace/Sources/DemoSpellCheckerBot/SpellChecker/YaSpellChecker.swift:18:54: warning: 'createNew' is deprecated: Please use the singleton EventLoopGroup explicitly
16 | var url = "https://speller.yandex.net/services/spellservice.json/checkText"
17 |
18 | let client = HTTPClient(eventLoopGroupProvider: .createNew)
| |- warning: 'createNew' is deprecated: Please use the singleton EventLoopGroup explicitly
| `- note: use 'singleton' instead
19 |
20 | func check(_ text: String, lang: Lang, format: Format) throws -> Future<[T]> {
[788/812] Emitting module DemoEchoBot
[789/812] Compiling DemoEchoBot main.swift
[790/812] Compiling DemoSpellCheckerBot main.swift
[791/812] Compiling DemoSpellCheckerBot SpellChecker.swift
[792/812] Emitting module DemoHelloBot
[793/812] Compiling DemoHelloBot NewMemberHandler.swift
[794/812] Compiling DemoHelloBot main.swift
[795/812] Emitting module DemoSpellCheckerBot
/host/spi-builder-workspace/Sources/DemoSpellCheckerBot/SpellChecker/YaSpellChecker.swift:18:54: warning: 'createNew' is deprecated: Please use the singleton EventLoopGroup explicitly
16 | var url = "https://speller.yandex.net/services/spellservice.json/checkText"
17 |
18 | let client = HTTPClient(eventLoopGroupProvider: .createNew)
| |- warning: 'createNew' is deprecated: Please use the singleton EventLoopGroup explicitly
| `- note: use 'singleton' instead
19 |
20 | func check(_ text: String, lang: Lang, format: Format) throws -> Future<[T]> {
[796/812] Compiling DemoSpellCheckerBot SpellCheckerController.swift
/host/spi-builder-workspace/Sources/DemoSpellCheckerBot/Controllers/SpellCheckerController.swift:149:60: warning: 'markdown' is deprecated: This is a legacy mode, retained for backward compatibility.
147 | messageId: message.messageId,
148 | text: text,
149 | parseMode: .markdown,
| |- warning: 'markdown' is deprecated: This is a legacy mode, retained for backward compatibility.
| `- note: use 'markdownV2' instead
150 | replyMarkup: markup)
151 | try bot.editMessageText(params: params)
/host/spi-builder-workspace/Sources/DemoSpellCheckerBot/Controllers/SpellCheckerController.swift:157:56: warning: 'markdown' is deprecated: This is a legacy mode, retained for backward compatibility.
155 | let params = Bot.SendMessageParams(chatId: .chat(message.chat.id),
156 | text: text,
157 | parseMode: .markdown,
| |- warning: 'markdown' is deprecated: This is a legacy mode, retained for backward compatibility.
| `- note: use 'markdownV2' instead
158 | replyMarkup: markup)
159 | try self.bot.sendMessage(params: params)
/host/spi-builder-workspace/Sources/DemoSpellCheckerBot/SpellChecker/YaSpellChecker.swift:18:54: warning: 'createNew' is deprecated: Please use the singleton EventLoopGroup explicitly
16 | var url = "https://speller.yandex.net/services/spellservice.json/checkText"
17 |
18 | let client = HTTPClient(eventLoopGroupProvider: .createNew)
| |- warning: 'createNew' is deprecated: Please use the singleton EventLoopGroup explicitly
| `- note: use 'singleton' instead
19 |
20 | func check(_ text: String, lang: Lang, format: Format) throws -> Future<[T]> {
[797/813] Compiling DemoSpellCheckerBot YaSpellFlow.swift
[799/815] Wrapping AST for DemoWebhooksLocally for debugging
[800/815] Write Objects.LinkFileList
[801/815] Wrapping AST for DemoSchedulerBot for debugging
[802/815] Write Objects.LinkFileList
[804/815] Wrapping AST for DemoEchoBot for debugging
[805/815] Write Objects.LinkFileList
[806/815] Wrapping AST for DemoSpellCheckerBot for debugging
[807/815] Write Objects.LinkFileList
[808/815] Wrapping AST for DemoHelloBot for debugging
[809/815] Write Objects.LinkFileList
[810/815] Linking SpellCheckerBot
[811/815] Linking WebhooksLocally
[812/815] Linking EchoBot
[813/815] Linking SchedulerBot
[814/815] Linking HelloBot
Build complete! (77.06s)
Build complete.
{
"dependencies" : [
{
"identity" : "swift-log",
"requirement" : {
"range" : [
{
"lower_bound" : "1.2.0",
"upper_bound" : "2.0.0"
}
]
},
"type" : "sourceControl",
"url" : "https://github.com/apple/swift-log.git"
},
{
"identity" : "async-http-client",
"requirement" : {
"range" : [
{
"lower_bound" : "1.1.0",
"upper_bound" : "2.0.0"
}
]
},
"type" : "sourceControl",
"url" : "https://github.com/swift-server/async-http-client.git"
},
{
"identity" : "swift-nio",
"requirement" : {
"range" : [
{
"lower_bound" : "2.18.0",
"upper_bound" : "3.0.0"
}
]
},
"type" : "sourceControl",
"url" : "https://github.com/apple/swift-nio.git"
}
],
"manifest_display_name" : "Telegrammer",
"name" : "Telegrammer",
"path" : "/host/spi-builder-workspace",
"platforms" : [
{
"name" : "macos",
"version" : "10.14"
}
],
"products" : [
{
"name" : "Telegrammer",
"targets" : [
"Telegrammer"
],
"type" : {
"library" : [
"automatic"
]
}
},
{
"name" : "TelegrammerMultipart",
"targets" : [
"TelegrammerMultipart"
],
"type" : {
"library" : [
"automatic"
]
}
},
{
"name" : "TelegrammerCMultipartParser",
"targets" : [
"TelegrammerCMultipartParser"
],
"type" : {
"library" : [
"automatic"
]
}
},
{
"name" : "EchoBot",
"targets" : [
"DemoEchoBot"
],
"type" : {
"executable" : null
}
},
{
"name" : "HelloBot",
"targets" : [
"DemoHelloBot"
],
"type" : {
"executable" : null
}
},
{
"name" : "SchedulerBot",
"targets" : [
"DemoSchedulerBot"
],
"type" : {
"executable" : null
}
},
{
"name" : "SpellCheckerBot",
"targets" : [
"DemoSpellCheckerBot"
],
"type" : {
"executable" : null
}
},
{
"name" : "WebhooksLocally",
"targets" : [
"DemoWebhooksLocally"
],
"type" : {
"executable" : null
}
}
],
"targets" : [
{
"c99name" : "TelegrammerTests",
"module_type" : "SwiftTarget",
"name" : "TelegrammerTests",
"path" : "Tests/TelegrammerTests",
"sources" : [
"FilterTests/EntityFilterTest.swift",
"FilterTests/PrivateFilterTest.swift",
"HandlerTests/CommandHandlerTest.swift",
"Helpers/Test+Helpers.swift",
"JobQueueTests/DailyJobTests.swift",
"JobQueueTests/JobQueueTests.swift",
"XCTestManifests.swift"
],
"target_dependencies" : [
"Telegrammer"
],
"type" : "test"
},
{
"c99name" : "TelegrammerMultipartTests",
"module_type" : "SwiftTarget",
"name" : "TelegrammerMultipartTests",
"path" : "Tests/TelegrammerMultipartTests",
"sources" : [
"MultipartKitTests.swift"
],
"target_dependencies" : [
"TelegrammerCMultipartParser"
],
"type" : "test"
},
{
"c99name" : "TelegrammerMultipart",
"module_type" : "SwiftTarget",
"name" : "TelegrammerMultipart",
"path" : "Sources/TelegrammerMultipart",
"product_dependencies" : [
"NIO",
"NIOHTTP1"
],
"product_memberships" : [
"Telegrammer",
"TelegrammerMultipart",
"EchoBot",
"HelloBot",
"SchedulerBot",
"SpellCheckerBot",
"WebhooksLocally"
],
"sources" : [
"BasicCodingKey.swift",
"Exports.swift",
"FormDataDecoder.swift",
"FormDataEncoder.swift",
"MultipartError.swift",
"MultipartParser.swift",
"MultipartPart.swift",
"MultipartPartConvertible.swift",
"MultipartSerializer.swift",
"Utilities.swift"
],
"target_dependencies" : [
"TelegrammerCMultipartParser"
],
"type" : "library"
},
{
"c99name" : "TelegrammerCMultipartParser",
"module_type" : "ClangTarget",
"name" : "TelegrammerCMultipartParser",
"path" : "Sources/TelegrammerCMultipartParser",
"product_memberships" : [
"Telegrammer",
"TelegrammerMultipart",
"TelegrammerCMultipartParser",
"EchoBot",
"HelloBot",
"SchedulerBot",
"SpellCheckerBot",
"WebhooksLocally"
],
"sources" : [
"multipartparser.c"
],
"type" : "library"
},
{
"c99name" : "Telegrammer",
"module_type" : "SwiftTarget",
"name" : "Telegrammer",
"path" : "Sources/Telegrammer",
"product_dependencies" : [
"AsyncHTTPClient",
"Logging"
],
"product_memberships" : [
"Telegrammer",
"EchoBot",
"HelloBot",
"SchedulerBot",
"SpellCheckerBot",
"WebhooksLocally"
],
"sources" : [
"Bot/BotProtocol.swift",
"Bot/Telegram/Bot.swift",
"Bot/Telegram/Extensions/Message+Helpers.swift",
"Bot/Telegram/Jobs/BasicJobQueue.swift",
"Bot/Telegram/Jobs/DailyJob.swift",
"Bot/Telegram/Jobs/Day.swift",
"Bot/Telegram/Jobs/Job.swift",
"Bot/Telegram/Jobs/JobQueue.swift",
"Bot/Telegram/Jobs/OnceJob.swift",
"Bot/Telegram/Jobs/RepeatableJob.swift",
"Bot/Telegram/Methods/Bot+addStickerToSet.swift",
"Bot/Telegram/Methods/Bot+answerCallbackQuery.swift",
"Bot/Telegram/Methods/Bot+answerInlineQuery.swift",
"Bot/Telegram/Methods/Bot+answerPreCheckoutQuery.swift",
"Bot/Telegram/Methods/Bot+answerShippingQuery.swift",
"Bot/Telegram/Methods/Bot+createNewStickerSet.swift",
"Bot/Telegram/Methods/Bot+deleteChatPhoto.swift",
"Bot/Telegram/Methods/Bot+deleteChatStickerSet.swift",
"Bot/Telegram/Methods/Bot+deleteMessage.swift",
"Bot/Telegram/Methods/Bot+deleteStickerFromSet.swift",
"Bot/Telegram/Methods/Bot+deleteWebhook.swift",
"Bot/Telegram/Methods/Bot+editMessageCaption.swift",
"Bot/Telegram/Methods/Bot+editMessageLiveLocation.swift",
"Bot/Telegram/Methods/Bot+editMessageMedia.swift",
"Bot/Telegram/Methods/Bot+editMessageReplyMarkup.swift",
"Bot/Telegram/Methods/Bot+editMessageText.swift",
"Bot/Telegram/Methods/Bot+exportChatInviteLink.swift",
"Bot/Telegram/Methods/Bot+forwardMessage.swift",
"Bot/Telegram/Methods/Bot+getChat.swift",
"Bot/Telegram/Methods/Bot+getChatAdministrators.swift",
"Bot/Telegram/Methods/Bot+getChatMember.swift",
"Bot/Telegram/Methods/Bot+getChatMembersCount.swift",
"Bot/Telegram/Methods/Bot+getFile.swift",
"Bot/Telegram/Methods/Bot+getGameHighScores.swift",
"Bot/Telegram/Methods/Bot+getMe.swift",
"Bot/Telegram/Methods/Bot+getMyCommands.swift",
"Bot/Telegram/Methods/Bot+getStickerSet.swift",
"Bot/Telegram/Methods/Bot+getUpdates.swift",
"Bot/Telegram/Methods/Bot+getUserProfilePhotos.swift",
"Bot/Telegram/Methods/Bot+getWebhookInfo.swift",
"Bot/Telegram/Methods/Bot+kickChatMember.swift",
"Bot/Telegram/Methods/Bot+leaveChat.swift",
"Bot/Telegram/Methods/Bot+pinChatMessage.swift",
"Bot/Telegram/Methods/Bot+promoteChatMember.swift",
"Bot/Telegram/Methods/Bot+restrictChatMember.swift",
"Bot/Telegram/Methods/Bot+sendAnimation.swift",
"Bot/Telegram/Methods/Bot+sendAudio.swift",
"Bot/Telegram/Methods/Bot+sendChatAction.swift",
"Bot/Telegram/Methods/Bot+sendContact.swift",
"Bot/Telegram/Methods/Bot+sendDice.swift",
"Bot/Telegram/Methods/Bot+sendDocument.swift",
"Bot/Telegram/Methods/Bot+sendGame.swift",
"Bot/Telegram/Methods/Bot+sendInvoice.swift",
"Bot/Telegram/Methods/Bot+sendLocation.swift",
"Bot/Telegram/Methods/Bot+sendMediaGroup.swift",
"Bot/Telegram/Methods/Bot+sendMessage.swift",
"Bot/Telegram/Methods/Bot+sendPhoto.swift",
"Bot/Telegram/Methods/Bot+sendPoll.swift",
"Bot/Telegram/Methods/Bot+sendSticker.swift",
"Bot/Telegram/Methods/Bot+sendVenue.swift",
"Bot/Telegram/Methods/Bot+sendVideo.swift",
"Bot/Telegram/Methods/Bot+sendVideoNote.swift",
"Bot/Telegram/Methods/Bot+sendVoice.swift",
"Bot/Telegram/Methods/Bot+setChatAdministratorCustomTitle.swift",
"Bot/Telegram/Methods/Bot+setChatDescription.swift",
"Bot/Telegram/Methods/Bot+setChatPermissions.swift",
"Bot/Telegram/Methods/Bot+setChatPhoto.swift",
"Bot/Telegram/Methods/Bot+setChatStickerSet.swift",
"Bot/Telegram/Methods/Bot+setChatTitle.swift",
"Bot/Telegram/Methods/Bot+setGameScore.swift",
"Bot/Telegram/Methods/Bot+setMyCommands.swift",
"Bot/Telegram/Methods/Bot+setPassportDataErrors.swift",
"Bot/Telegram/Methods/Bot+setStickerPositionInSet.swift",
"Bot/Telegram/Methods/Bot+setStickerSetThumb.swift",
"Bot/Telegram/Methods/Bot+setWebhook.swift",
"Bot/Telegram/Methods/Bot+stopMessageLiveLocation.swift",
"Bot/Telegram/Methods/Bot+stopPoll.swift",
"Bot/Telegram/Methods/Bot+unbanChatMember.swift",
"Bot/Telegram/Methods/Bot+unpinChatMessage.swift",
"Bot/Telegram/Methods/Bot+uploadStickerFile.swift",
"Bot/Telegram/Models/Animation.swift",
"Bot/Telegram/Models/Audio.swift",
"Bot/Telegram/Models/BotCommand.swift",
"Bot/Telegram/Models/CallbackGame.swift",
"Bot/Telegram/Models/CallbackQuery.swift",
"Bot/Telegram/Models/Chat.swift",
"Bot/Telegram/Models/ChatMember.swift",
"Bot/Telegram/Models/ChatPermissions.swift",
"Bot/Telegram/Models/ChatPhoto.swift",
"Bot/Telegram/Models/ChosenInlineResult.swift",
"Bot/Telegram/Models/Contact.swift",
"Bot/Telegram/Models/Dice.swift",
"Bot/Telegram/Models/Document.swift",
"Bot/Telegram/Models/EncryptedCredentials.swift",
"Bot/Telegram/Models/EncryptedPassportElement.swift",
"Bot/Telegram/Models/File.swift",
"Bot/Telegram/Models/ForceReply.swift",
"Bot/Telegram/Models/Game.swift",
"Bot/Telegram/Models/GameHighScore.swift",
"Bot/Telegram/Models/InlineKeyboardButton.swift",
"Bot/Telegram/Models/InlineKeyboardMarkup.swift",
"Bot/Telegram/Models/InlineQuery.swift",
"Bot/Telegram/Models/InlineQueryResultArticle.swift",
"Bot/Telegram/Models/InlineQueryResultAudio.swift",
"Bot/Telegram/Models/InlineQueryResultCachedAudio.swift",
"Bot/Telegram/Models/InlineQueryResultCachedDocument.swift",
"Bot/Telegram/Models/InlineQueryResultCachedGif.swift",
"Bot/Telegram/Models/InlineQueryResultCachedMpeg4Gif.swift",
"Bot/Telegram/Models/InlineQueryResultCachedPhoto.swift",
"Bot/Telegram/Models/InlineQueryResultCachedSticker.swift",
"Bot/Telegram/Models/InlineQueryResultCachedVideo.swift",
"Bot/Telegram/Models/InlineQueryResultCachedVoice.swift",
"Bot/Telegram/Models/InlineQueryResultContact.swift",
"Bot/Telegram/Models/InlineQueryResultDocument.swift",
"Bot/Telegram/Models/InlineQueryResultGame.swift",
"Bot/Telegram/Models/InlineQueryResultGif.swift",
"Bot/Telegram/Models/InlineQueryResultLocation.swift",
"Bot/Telegram/Models/InlineQueryResultMpeg4Gif.swift",
"Bot/Telegram/Models/InlineQueryResultPhoto.swift",
"Bot/Telegram/Models/InlineQueryResultVenue.swift",
"Bot/Telegram/Models/InlineQueryResultVideo.swift",
"Bot/Telegram/Models/InlineQueryResultVoice.swift",
"Bot/Telegram/Models/InputContactMessageContent.swift",
"Bot/Telegram/Models/InputLocationMessageContent.swift",
"Bot/Telegram/Models/InputMediaAnimation.swift",
"Bot/Telegram/Models/InputMediaAudio.swift",
"Bot/Telegram/Models/InputMediaDocument.swift",
"Bot/Telegram/Models/InputMediaPhoto.swift",
"Bot/Telegram/Models/InputMediaVideo.swift",
"Bot/Telegram/Models/InputTextMessageContent.swift",
"Bot/Telegram/Models/InputVenueMessageContent.swift",
"Bot/Telegram/Models/Invoice.swift",
"Bot/Telegram/Models/KeyboardButton.swift",
"Bot/Telegram/Models/KeyboardButtonPollType.swift",
"Bot/Telegram/Models/LabeledPrice.swift",
"Bot/Telegram/Models/Location.swift",
"Bot/Telegram/Models/LoginUrl.swift",
"Bot/Telegram/Models/MaskPosition.swift",
"Bot/Telegram/Models/Message.swift",
"Bot/Telegram/Models/MessageEntity.swift",
"Bot/Telegram/Models/OrderInfo.swift",
"Bot/Telegram/Models/PassportData.swift",
"Bot/Telegram/Models/PassportElementErrorDataField.swift",
"Bot/Telegram/Models/PassportElementErrorFile.swift",
"Bot/Telegram/Models/PassportElementErrorFiles.swift",
"Bot/Telegram/Models/PassportElementErrorFrontSide.swift",
"Bot/Telegram/Models/PassportElementErrorReverseSide.swift",
"Bot/Telegram/Models/PassportElementErrorSelfie.swift",
"Bot/Telegram/Models/PassportElementErrorTranslationFile.swift",
"Bot/Telegram/Models/PassportElementErrorTranslationFiles.swift",
"Bot/Telegram/Models/PassportElementErrorUnspecified.swift",
"Bot/Telegram/Models/PassportFile.swift",
"Bot/Telegram/Models/PhotoSize.swift",
"Bot/Telegram/Models/Poll.swift",
"Bot/Telegram/Models/PollAnswer.swift",
"Bot/Telegram/Models/PollOption.swift",
"Bot/Telegram/Models/PreCheckoutQuery.swift",
"Bot/Telegram/Models/ReplyKeyboardMarkup.swift",
"Bot/Telegram/Models/ReplyKeyboardRemove.swift",
"Bot/Telegram/Models/ResponseParameters.swift",
"Bot/Telegram/Models/ShippingAddress.swift",
"Bot/Telegram/Models/ShippingOption.swift",
"Bot/Telegram/Models/ShippingQuery.swift",
"Bot/Telegram/Models/Sticker.swift",
"Bot/Telegram/Models/StickerSet.swift",
"Bot/Telegram/Models/SuccessfulPayment.swift",
"Bot/Telegram/Models/Update.swift",
"Bot/Telegram/Models/User.swift",
"Bot/Telegram/Models/UserProfilePhotos.swift",
"Bot/Telegram/Models/Venue.swift",
"Bot/Telegram/Models/Video.swift",
"Bot/Telegram/Models/VideoNote.swift",
"Bot/Telegram/Models/Voice.swift",
"Bot/Telegram/Models/WebhookInfo.swift",
"Bot/Telegram/Storage/Storage.swift",
"Dispatcher/Dispatcher.swift",
"Dispatcher/HandlerGroup.swift",
"Dispatcher/HandlersQueue.swift",
"Errors/BotError.swift",
"Filters/AllFilter.swift",
"Filters/AudioFilter.swift",
"Filters/CaptionEntityFilter.swift",
"Filters/ChatFilter.swift",
"Filters/CommandFilter.swift",
"Filters/ContactFilter.swift",
"Filters/DocumentFilter.swift",
"Filters/EntityFilter.swift",
"Filters/Filter.swift",
"Filters/ForwarderFilter.swift",
"Filters/GameFilter.swift",
"Filters/GroupFilter.swift",
"Filters/InvoiceFilter.swift",
"Filters/LanguageFilter.swift",
"Filters/LocationFilter.swift",
"Filters/PhotoFilter.swift",
"Filters/PrivateFilter.swift",
"Filters/RegexpFilter.swift",
"Filters/ReplyFilter.swift",
"Filters/StatusUpdateFilters.swift",
"Filters/StickerFilter.swift",
"Filters/SuccesfulPaymentFilter.swift",
"Filters/TextFilter.swift",
"Filters/UserFilter.swift",
"Filters/VenueFilter.swift",
"Filters/VideoFilter.swift",
"Filters/VideoNoteFilter.swift",
"Filters/VoiceFilter.swift",
"Handlers/CallbackQueryHandler.swift",
"Handlers/CommandHandler.swift",
"Handlers/ConversationHandler.swift",
"Handlers/Handler.swift",
"Handlers/LoggerHandler.swift",
"Handlers/MessageHandler.swift",
"Handlers/RegexpHandler.swift",
"Helpers/Constants.swift",
"Helpers/Enviroment+Helper.swift",
"Helpers/Error+Helpers.swift",
"Helpers/HTTPHeader+Helper.swift",
"Helpers/HTTPRequest+Helper.swift",
"Helpers/MultipartPartConvertible+Helper.swift",
"Helpers/String+Helper.swift",
"Helpers/SynchronizedArray.swift",
"Helpers/TimeAmount+Helpers.swift",
"Network/Bot.Settings+Proxy.swift",
"Network/BotClient.swift",
"Network/Longpolling.swift",
"Network/Network.swift",
"Network/UpdatesServer.swift",
"Network/Webhooks.swift",
"Types/ChatId.swift",
"Types/ChatType.swift",
"Types/FileInfo.swift",
"Types/InlineQueryResult.swift",
"Types/InputFile.swift",
"Types/InputMedia.swift",
"Types/InputMessageContent.swift",
"Types/MessageEntityType.swift",
"Types/MessageOrBool.swift",
"Types/ParseMode.swift",
"Types/PassportElementError.swift",
"Types/ReplyMarkup.swift",
"Types/TelegramContainer.swift",
"Types/TelegramEncodables.swift",
"Updater/Updater.swift"
],
"target_dependencies" : [
"TelegrammerMultipart"
],
"type" : "library"
},
{
"c99name" : "DemoWebhooksLocally",
"module_type" : "SwiftTarget",
"name" : "DemoWebhooksLocally",
"path" : "Sources/DemoWebhooksLocally",
"product_memberships" : [
"WebhooksLocally"
],
"sources" : [
"main.swift"
],
"target_dependencies" : [
"Telegrammer"
],
"type" : "executable"
},
{
"c99name" : "DemoSpellCheckerBot",
"module_type" : "SwiftTarget",
"name" : "DemoSpellCheckerBot",
"path" : "Sources/DemoSpellCheckerBot",
"product_memberships" : [
"SpellCheckerBot"
],
"sources" : [
"Controllers/SpellCheckerController.swift",
"Helpers/Array+Helper.swift",
"SpellChecker/SpellChecker.swift",
"SpellChecker/YaSpellCheck.swift",
"SpellChecker/YaSpellChecker.swift",
"SpellChecker/YaSpellFlow.swift",
"main.swift"
],
"target_dependencies" : [
"Telegrammer"
],
"type" : "executable"
},
{
"c99name" : "DemoSchedulerBot",
"module_type" : "SwiftTarget",
"name" : "DemoSchedulerBot",
"path" : "Sources/DemoSchedulerBot",
"product_memberships" : [
"SchedulerBot"
],
"sources" : [
"main.swift"
],
"target_dependencies" : [
"Telegrammer"
],
"type" : "executable"
},
{
"c99name" : "DemoHelloBot",
"module_type" : "SwiftTarget",
"name" : "DemoHelloBot",
"path" : "Sources/DemoHelloBot",
"product_memberships" : [
"HelloBot"
],
"sources" : [
"Handlers/NewMemberHandler.swift",
"main.swift"
],
"target_dependencies" : [
"Telegrammer"
],
"type" : "executable"
},
{
"c99name" : "DemoEchoBot",
"module_type" : "SwiftTarget",
"name" : "DemoEchoBot",
"path" : "Sources/DemoEchoBot",
"product_memberships" : [
"EchoBot"
],
"sources" : [
"main.swift"
],
"target_dependencies" : [
"Telegrammer"
],
"type" : "executable"
}
],
"tools_version" : "5.2"
}
basic-6.1-latest: Pulling from finestructure/spi-images
Digest: sha256:3bdcac04179f4ed3e5b8e9dbd6e74bbf5ebc0f4fde48bbaad7d1e5c757e65bcb
Status: Image is up to date for registry.gitlab.com/finestructure/spi-images:basic-6.1-latest
Done.