Swift Package IndexBuild Information
Failed to build Telegrammer, reference master (459176), with Swift 6.0 for macOS (SPM) on 27 Nov 2024 09:12:15 UTC.
Build Command
env DEVELOPER_DIR=/Applications/Xcode-16.1.0.app xcrun swift build --arch arm64 -Xswiftc -Xfrontend -Xswiftc -stats-output-dir -Xswiftc -Xfrontend -Xswiftc .stats -Xswiftc -strict-concurrency=complete -Xswiftc -enable-upcoming-feature -Xswiftc StrictConcurrency -Xswiftc -enable-upcoming-feature -Xswiftc DisableOutwardActorInference -Xswiftc -enable-upcoming-feature -Xswiftc GlobalActorIsolatedTypesUsability -Xswiftc -enable-upcoming-feature -Xswiftc InferSendableFromCapturesBuild Log
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+setMyCommands.swift:44:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
42 | */
43 | @discardableResult
44 | func setMyCommands(params: SetMyCommandsParams) 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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+setWebhook.swift:61:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
59 | */
60 | @discardableResult
61 | func setWebhook(params: SetWebhookParams) throws -> Future<Bool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
62 | let body = try httpBody(for: params)
63 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+unbanChatMember.swift:44:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
42 | */
43 | @discardableResult
44 | func unbanChatMember(params: UnbanChatMemberParams) 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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+unpinAllChatMessages.swift:34:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
32 | */
33 | @discardableResult
34 | func unpinAllChatMessages(params: UnpinAllChatMessagesParams) 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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+unpinChatMessage.swift:39:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
37 | */
38 | @discardableResult
39 | func unpinChatMessage(params: UnpinChatMessageParams) 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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
[933/977] Compiling Telegrammer Bot+unpinChatMessage.swift
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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<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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+setMyCommands.swift:44:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
42 | */
43 | @discardableResult
44 | func setMyCommands(params: SetMyCommandsParams) 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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+setWebhook.swift:61:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
59 | */
60 | @discardableResult
61 | func setWebhook(params: SetWebhookParams) throws -> Future<Bool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
62 | let body = try httpBody(for: params)
63 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+unbanChatMember.swift:44:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
42 | */
43 | @discardableResult
44 | func unbanChatMember(params: UnbanChatMemberParams) 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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+unpinAllChatMessages.swift:34:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
32 | */
33 | @discardableResult
34 | func unpinAllChatMessages(params: UnpinAllChatMessagesParams) 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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+unpinChatMessage.swift:39:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
37 | */
38 | @discardableResult
39 | func unpinChatMessage(params: UnpinChatMessageParams) 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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
[934/977] Compiling Telegrammer Bot+uploadStickerFile.swift
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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<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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+setMyCommands.swift:44:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
42 | */
43 | @discardableResult
44 | func setMyCommands(params: SetMyCommandsParams) 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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+setWebhook.swift:61:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
59 | */
60 | @discardableResult
61 | func setWebhook(params: SetWebhookParams) throws -> Future<Bool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
62 | let body = try httpBody(for: params)
63 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+unbanChatMember.swift:44:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
42 | */
43 | @discardableResult
44 | func unbanChatMember(params: UnbanChatMemberParams) 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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+unpinAllChatMessages.swift:34:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
32 | */
33 | @discardableResult
34 | func unpinAllChatMessages(params: UnpinAllChatMessagesParams) 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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+unpinChatMessage.swift:39:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
37 | */
38 | @discardableResult
39 | func unpinChatMessage(params: UnpinChatMessageParams) 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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
[935/977] Compiling Telegrammer Animation.swift
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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<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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+setMyCommands.swift:44:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
42 | */
43 | @discardableResult
44 | func setMyCommands(params: SetMyCommandsParams) 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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+setWebhook.swift:61:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
59 | */
60 | @discardableResult
61 | func setWebhook(params: SetWebhookParams) throws -> Future<Bool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
62 | let body = try httpBody(for: params)
63 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+unbanChatMember.swift:44:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
42 | */
43 | @discardableResult
44 | func unbanChatMember(params: UnbanChatMemberParams) 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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+unpinAllChatMessages.swift:34:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
32 | */
33 | @discardableResult
34 | func unpinAllChatMessages(params: UnpinAllChatMessagesParams) 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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+unpinChatMessage.swift:39:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
37 | */
38 | @discardableResult
39 | func unpinChatMessage(params: UnpinChatMessageParams) 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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
[936/977] Compiling Telegrammer Audio.swift
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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<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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+setMyCommands.swift:44:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
42 | */
43 | @discardableResult
44 | func setMyCommands(params: SetMyCommandsParams) 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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+setWebhook.swift:61:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
59 | */
60 | @discardableResult
61 | func setWebhook(params: SetWebhookParams) throws -> Future<Bool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
62 | let body = try httpBody(for: params)
63 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+unbanChatMember.swift:44:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
42 | */
43 | @discardableResult
44 | func unbanChatMember(params: UnbanChatMemberParams) 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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+unpinAllChatMessages.swift:34:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
32 | */
33 | @discardableResult
34 | func unpinAllChatMessages(params: UnpinAllChatMessagesParams) 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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+unpinChatMessage.swift:39:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
37 | */
38 | @discardableResult
39 | func unpinChatMessage(params: UnpinChatMessageParams) 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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
[937/977] Compiling Telegrammer BotCommand.swift
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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<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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+setMyCommands.swift:44:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
42 | */
43 | @discardableResult
44 | func setMyCommands(params: SetMyCommandsParams) 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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+setWebhook.swift:61:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
59 | */
60 | @discardableResult
61 | func setWebhook(params: SetWebhookParams) throws -> Future<Bool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
62 | let body = try httpBody(for: params)
63 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+unbanChatMember.swift:44:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
42 | */
43 | @discardableResult
44 | func unbanChatMember(params: UnbanChatMemberParams) 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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+unpinAllChatMessages.swift:34:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
32 | */
33 | @discardableResult
34 | func unpinAllChatMessages(params: UnpinAllChatMessagesParams) 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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+unpinChatMessage.swift:39:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
37 | */
38 | @discardableResult
39 | func unpinChatMessage(params: UnpinChatMessageParams) 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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
[938/977] Compiling Telegrammer BotCommandScope.swift
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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<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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+setMyCommands.swift:44:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
42 | */
43 | @discardableResult
44 | func setMyCommands(params: SetMyCommandsParams) 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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+setWebhook.swift:61:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
59 | */
60 | @discardableResult
61 | func setWebhook(params: SetWebhookParams) throws -> Future<Bool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
62 | let body = try httpBody(for: params)
63 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+unbanChatMember.swift:44:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
42 | */
43 | @discardableResult
44 | func unbanChatMember(params: UnbanChatMemberParams) 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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+unpinAllChatMessages.swift:34:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
32 | */
33 | @discardableResult
34 | func unpinAllChatMessages(params: UnpinAllChatMessagesParams) 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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+unpinChatMessage.swift:39:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
37 | */
38 | @discardableResult
39 | func unpinChatMessage(params: UnpinChatMessageParams) 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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
[939/977] Compiling Telegrammer BotCommandScopeAllChatAdministrators.swift
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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<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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+setMyCommands.swift:44:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
42 | */
43 | @discardableResult
44 | func setMyCommands(params: SetMyCommandsParams) 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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+setWebhook.swift:61:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
59 | */
60 | @discardableResult
61 | func setWebhook(params: SetWebhookParams) throws -> Future<Bool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
62 | let body = try httpBody(for: params)
63 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+unbanChatMember.swift:44:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
42 | */
43 | @discardableResult
44 | func unbanChatMember(params: UnbanChatMemberParams) 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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+unpinAllChatMessages.swift:34:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
32 | */
33 | @discardableResult
34 | func unpinAllChatMessages(params: UnpinAllChatMessagesParams) 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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+unpinChatMessage.swift:39:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
37 | */
38 | @discardableResult
39 | func unpinChatMessage(params: UnpinChatMessageParams) 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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
/Users/admin/builder/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)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: type declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: type declared here
374 | // 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.
375 | @usableFromInline
[940/977] Compiling Telegrammer LoginUrl.swift
[941/977] Compiling Telegrammer MaskPosition.swift
[942/977] Compiling Telegrammer Message.swift
[943/977] Compiling Telegrammer MessageAutoDeleteTimerChanged.swift
[944/977] Compiling Telegrammer MessageEntity.swift
[945/977] Compiling Telegrammer MessageId.swift
[946/977] Compiling Telegrammer OrderInfo.swift
[947/977] Compiling Telegrammer PassportData.swift
[948/977] Compiling Telegrammer PassportElementErrorDataField.swift
[949/977] Compiling Telegrammer PassportElementErrorFile.swift
[950/977] Compiling Telegrammer PassportElementErrorFiles.swift
[951/977] Compiling Telegrammer PassportElementErrorFrontSide.swift
[952/977] Compiling Telegrammer PassportElementErrorReverseSide.swift
[953/977] Compiling Telegrammer PassportElementErrorSelfie.swift
[954/977] Compiling Telegrammer PassportElementErrorTranslationFile.swift
[955/977] Compiling Telegrammer PassportElementErrorTranslationFiles.swift
[956/977] Compiling Telegrammer PassportElementErrorUnspecified.swift
[957/977] Compiling Telegrammer PassportFile.swift
[958/977] Compiling Telegrammer PhotoSize.swift
[959/977] Compiling Telegrammer Poll.swift
[960/977] Compiling Telegrammer PollAnswer.swift
[961/977] Compiling Telegrammer PollOption.swift
[962/977] Compiling Telegrammer PreCheckoutQuery.swift
[963/994] Compiling DemoWebhooksLocally main.swift
[964/994] Emitting module DemoWebhooksLocally
[964/994] Write Objects.LinkFileList
error: emit-module command failed with exit code 1 (use -v to see invocation)
[966/994] Emitting module DemoEchoBot
/Users/admin/builder/spi-builder-workspace/Sources/DemoEchoBot/main.swift:66:55: warning: reference to class property 'text' is not concurrency-safe because it involves shared mutable state; this is an error in the Swift 6 language mode
64 |
65 | ///Creating and adding handler for ordinary text messages
66 | let echoHandler = MessageHandler(filters: Filters.text, callback: echoResponse)
| `- warning: reference to class property 'text' is not concurrency-safe because it involves shared mutable state; this is an error in the Swift 6 language mode
67 | dispatcher.add(handler: echoHandler)
68 |
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Filters/TextFilter.swift:22:16: note: class property declared here
20 |
21 | public extension Filters {
22 | static var text = Filters(filter: TextFilter())
| `- note: class property declared here
23 | }
24 |
/Users/admin/builder/spi-builder-workspace/Sources/DemoEchoBot/main.swift:32:17: error: main actor-isolated var 'userEchoModes' can not be referenced from a nonisolated context
22 |
23 | /// Dictionary for user echo modes
24 | var userEchoModes: [Int64: Bool] = [:]
| `- note: var declared here
25 |
26 | ///Callback for Command handler, which send Echo mode status for user
27 | func echoModeSwitch(_ update: Update, _ context: BotContext?) throws {
| `- note: add '@MainActor' to make global function 'echoModeSwitch' part of global actor 'MainActor'
28 | guard let message = update.message,
29 | let user = message.from else { return }
30 |
31 | var onText = ""
32 | if let on = userEchoModes[user.id] {
| `- error: main actor-isolated var 'userEchoModes' can not be referenced from a nonisolated context
33 | onText = on ? "OFF" : "ON"
34 | userEchoModes[user.id] = !on
/Users/admin/builder/spi-builder-workspace/Sources/DemoEchoBot/main.swift:34:9: error: main actor-isolated var 'userEchoModes' can not be mutated from a nonisolated context
22 |
23 | /// Dictionary for user echo modes
24 | var userEchoModes: [Int64: Bool] = [:]
| `- note: mutation of this var is only permitted within the actor
25 |
26 | ///Callback for Command handler, which send Echo mode status for user
27 | func echoModeSwitch(_ update: Update, _ context: BotContext?) throws {
| `- note: add '@MainActor' to make global function 'echoModeSwitch' part of global actor 'MainActor'
28 | guard let message = update.message,
29 | let user = message.from else { return }
:
32 | if let on = userEchoModes[user.id] {
33 | onText = on ? "OFF" : "ON"
34 | userEchoModes[user.id] = !on
| `- error: main actor-isolated var 'userEchoModes' can not be mutated from a nonisolated context
35 | } else {
36 | onText = "ON"
/Users/admin/builder/spi-builder-workspace/Sources/DemoEchoBot/main.swift:37:9: error: main actor-isolated var 'userEchoModes' can not be mutated from a nonisolated context
22 |
23 | /// Dictionary for user echo modes
24 | var userEchoModes: [Int64: Bool] = [:]
| `- note: mutation of this var is only permitted within the actor
25 |
26 | ///Callback for Command handler, which send Echo mode status for user
27 | func echoModeSwitch(_ update: Update, _ context: BotContext?) throws {
| `- note: add '@MainActor' to make global function 'echoModeSwitch' part of global actor 'MainActor'
28 | guard let message = update.message,
29 | let user = message.from else { return }
:
35 | } else {
36 | onText = "ON"
37 | userEchoModes[user.id] = true
| `- error: main actor-isolated var 'userEchoModes' can not be mutated from a nonisolated context
38 | }
39 |
/Users/admin/builder/spi-builder-workspace/Sources/DemoEchoBot/main.swift:44:9: warning: main actor-isolated let 'bot' can not be referenced from a nonisolated context; this is an error in the Swift 6 language mode
19 | //)
20 |
21 | let bot = try! Bot(settings: settings)
| `- note: let declared here
22 |
23 | /// Dictionary for user echo modes
:
25 |
26 | ///Callback for Command handler, which send Echo mode status for user
27 | func echoModeSwitch(_ update: Update, _ context: BotContext?) throws {
| `- note: add '@MainActor' to make global function 'echoModeSwitch' part of global actor 'MainActor'
28 | guard let message = update.message,
29 | let user = message.from else { return }
:
42 | text: "Echo mode turned \(onText)"
43 | )
44 | try bot.sendMessage(params: params)
| `- warning: main actor-isolated let 'bot' can not be referenced from a nonisolated context; this is an error in the Swift 6 language mode
45 | }
46 |
/Users/admin/builder/spi-builder-workspace/Sources/DemoEchoBot/main.swift:51:18: error: main actor-isolated var 'userEchoModes' can not be referenced from a nonisolated context
22 |
23 | /// Dictionary for user echo modes
24 | var userEchoModes: [Int64: Bool] = [:]
| `- note: var declared here
25 |
26 | ///Callback for Command handler, which send Echo mode status for user
:
46 |
47 | ///Callback for Message handler, which send echo message to user
48 | func echoResponse(_ update: Update, _ context: BotContext?) throws {
| `- note: add '@MainActor' to make global function 'echoResponse' part of global actor 'MainActor'
49 | guard let message = update.message,
50 | let user = message.from,
51 | let on = userEchoModes[user.id],
| `- error: main actor-isolated var 'userEchoModes' can not be referenced from a nonisolated context
52 | on == true else { return }
53 | let params = Bot.SendMessageParams(chatId: .chat(message.chat.id), text: message.text!)
/Users/admin/builder/spi-builder-workspace/Sources/DemoEchoBot/main.swift:54:9: warning: main actor-isolated let 'bot' can not be referenced from a nonisolated context; this is an error in the Swift 6 language mode
19 | //)
20 |
21 | let bot = try! Bot(settings: settings)
| `- note: let declared here
22 |
23 | /// Dictionary for user echo modes
:
46 |
47 | ///Callback for Message handler, which send echo message to user
48 | func echoResponse(_ update: Update, _ context: BotContext?) throws {
| `- note: add '@MainActor' to make global function 'echoResponse' part of global actor 'MainActor'
49 | guard let message = update.message,
50 | let user = message.from,
:
52 | on == true else { return }
53 | let params = Bot.SendMessageParams(chatId: .chat(message.chat.id), text: message.text!)
54 | try bot.sendMessage(params: params)
| `- warning: main actor-isolated let 'bot' can not be referenced from a nonisolated context; this is an error in the Swift 6 language mode
55 | }
56 |
[967/994] Compiling DemoEchoBot main.swift
/Users/admin/builder/spi-builder-workspace/Sources/DemoEchoBot/main.swift:66:55: warning: reference to class property 'text' is not concurrency-safe because it involves shared mutable state; this is an error in the Swift 6 language mode
64 |
65 | ///Creating and adding handler for ordinary text messages
66 | let echoHandler = MessageHandler(filters: Filters.text, callback: echoResponse)
| `- warning: reference to class property 'text' is not concurrency-safe because it involves shared mutable state; this is an error in the Swift 6 language mode
67 | dispatcher.add(handler: echoHandler)
68 |
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Filters/TextFilter.swift:22:16: note: class property declared here
20 |
21 | public extension Filters {
22 | static var text = Filters(filter: TextFilter())
| `- note: class property declared here
23 | }
24 |
/Users/admin/builder/spi-builder-workspace/Sources/DemoEchoBot/main.swift:32:17: error: main actor-isolated var 'userEchoModes' can not be referenced from a nonisolated context
22 |
23 | /// Dictionary for user echo modes
24 | var userEchoModes: [Int64: Bool] = [:]
| `- note: var declared here
25 |
26 | ///Callback for Command handler, which send Echo mode status for user
27 | func echoModeSwitch(_ update: Update, _ context: BotContext?) throws {
| `- note: add '@MainActor' to make global function 'echoModeSwitch' part of global actor 'MainActor'
28 | guard let message = update.message,
29 | let user = message.from else { return }
30 |
31 | var onText = ""
32 | if let on = userEchoModes[user.id] {
| `- error: main actor-isolated var 'userEchoModes' can not be referenced from a nonisolated context
33 | onText = on ? "OFF" : "ON"
34 | userEchoModes[user.id] = !on
/Users/admin/builder/spi-builder-workspace/Sources/DemoEchoBot/main.swift:34:9: error: main actor-isolated var 'userEchoModes' can not be mutated from a nonisolated context
22 |
23 | /// Dictionary for user echo modes
24 | var userEchoModes: [Int64: Bool] = [:]
| `- note: mutation of this var is only permitted within the actor
25 |
26 | ///Callback for Command handler, which send Echo mode status for user
27 | func echoModeSwitch(_ update: Update, _ context: BotContext?) throws {
| `- note: add '@MainActor' to make global function 'echoModeSwitch' part of global actor 'MainActor'
28 | guard let message = update.message,
29 | let user = message.from else { return }
:
32 | if let on = userEchoModes[user.id] {
33 | onText = on ? "OFF" : "ON"
34 | userEchoModes[user.id] = !on
| `- error: main actor-isolated var 'userEchoModes' can not be mutated from a nonisolated context
35 | } else {
36 | onText = "ON"
/Users/admin/builder/spi-builder-workspace/Sources/DemoEchoBot/main.swift:37:9: error: main actor-isolated var 'userEchoModes' can not be mutated from a nonisolated context
22 |
23 | /// Dictionary for user echo modes
24 | var userEchoModes: [Int64: Bool] = [:]
| `- note: mutation of this var is only permitted within the actor
25 |
26 | ///Callback for Command handler, which send Echo mode status for user
27 | func echoModeSwitch(_ update: Update, _ context: BotContext?) throws {
| `- note: add '@MainActor' to make global function 'echoModeSwitch' part of global actor 'MainActor'
28 | guard let message = update.message,
29 | let user = message.from else { return }
:
35 | } else {
36 | onText = "ON"
37 | userEchoModes[user.id] = true
| `- error: main actor-isolated var 'userEchoModes' can not be mutated from a nonisolated context
38 | }
39 |
/Users/admin/builder/spi-builder-workspace/Sources/DemoEchoBot/main.swift:44:9: warning: main actor-isolated let 'bot' can not be referenced from a nonisolated context; this is an error in the Swift 6 language mode
19 | //)
20 |
21 | let bot = try! Bot(settings: settings)
| `- note: let declared here
22 |
23 | /// Dictionary for user echo modes
:
25 |
26 | ///Callback for Command handler, which send Echo mode status for user
27 | func echoModeSwitch(_ update: Update, _ context: BotContext?) throws {
| `- note: add '@MainActor' to make global function 'echoModeSwitch' part of global actor 'MainActor'
28 | guard let message = update.message,
29 | let user = message.from else { return }
:
42 | text: "Echo mode turned \(onText)"
43 | )
44 | try bot.sendMessage(params: params)
| `- warning: main actor-isolated let 'bot' can not be referenced from a nonisolated context; this is an error in the Swift 6 language mode
45 | }
46 |
/Users/admin/builder/spi-builder-workspace/Sources/DemoEchoBot/main.swift:51:18: error: main actor-isolated var 'userEchoModes' can not be referenced from a nonisolated context
22 |
23 | /// Dictionary for user echo modes
24 | var userEchoModes: [Int64: Bool] = [:]
| `- note: var declared here
25 |
26 | ///Callback for Command handler, which send Echo mode status for user
:
46 |
47 | ///Callback for Message handler, which send echo message to user
48 | func echoResponse(_ update: Update, _ context: BotContext?) throws {
| `- note: add '@MainActor' to make global function 'echoResponse' part of global actor 'MainActor'
49 | guard let message = update.message,
50 | let user = message.from,
51 | let on = userEchoModes[user.id],
| `- error: main actor-isolated var 'userEchoModes' can not be referenced from a nonisolated context
52 | on == true else { return }
53 | let params = Bot.SendMessageParams(chatId: .chat(message.chat.id), text: message.text!)
/Users/admin/builder/spi-builder-workspace/Sources/DemoEchoBot/main.swift:54:9: warning: main actor-isolated let 'bot' can not be referenced from a nonisolated context; this is an error in the Swift 6 language mode
19 | //)
20 |
21 | let bot = try! Bot(settings: settings)
| `- note: let declared here
22 |
23 | /// Dictionary for user echo modes
:
46 |
47 | ///Callback for Message handler, which send echo message to user
48 | func echoResponse(_ update: Update, _ context: BotContext?) throws {
| `- note: add '@MainActor' to make global function 'echoResponse' part of global actor 'MainActor'
49 | guard let message = update.message,
50 | let user = message.from,
:
52 | on == true else { return }
53 | let params = Bot.SendMessageParams(chatId: .chat(message.chat.id), text: message.text!)
54 | try bot.sendMessage(params: params)
| `- warning: main actor-isolated let 'bot' can not be referenced from a nonisolated context; this is an error in the Swift 6 language mode
55 | }
56 |
[968/994] Compiling DemoHelloBot NewMemberHandler.swift
/Users/admin/builder/spi-builder-workspace/Sources/DemoHelloBot/main.swift:42:13: warning: main actor-isolated let 'bot' can not be referenced from a nonisolated context; this is an error in the Swift 6 language mode
19 | //)
20 |
21 | let bot = try! Bot(settings: settings)
| `- note: let declared here
22 |
23 | ///Callback for handler, that sends Hello message for new chat member
24 | func greetNewMember(_ update: Update) throws {
| `- note: add '@MainActor' to make global function 'greetNewMember' part of global actor 'MainActor'
25 | guard let message = update.message,
26 | let newUsers = message.newChatMembers else { return }
:
40 | Here you may ask any questions about me!
41 | """)
42 | try bot.sendMessage(params: params)
| `- warning: main actor-isolated let 'bot' can not be referenced from a nonisolated context; this is an error in the Swift 6 language mode
43 | }
44 | }
/Users/admin/builder/spi-builder-workspace/Sources/DemoSchedulerBot/main.swift:45:13: warning: main actor-isolated let 'bot' can not be referenced from a nonisolated context; this is an error in the Swift 6 language mode
22 | //)
23 |
24 | let bot = try! Bot(settings: settings)
| `- note: let declared here
25 | let jobQueue = BasicJobQueue<Chat>(bot: bot)
26 |
:
43 | text: "Once, after \(interval) seconds: \(Date())"
44 | )
45 | try bot.sendMessage(params: params)
| `- warning: main actor-isolated let 'bot' can not be referenced from a nonisolated context; this is an error in the Swift 6 language mode
46 | }
47 |
[968/994] Linking WebhooksLocally
BUILD FAILURE 6.0 macosSpm