Telegrammer – Build Information – Swift Package Index

Has it really been five years since Swift Package Index launched? Read our anniversary blog post!

Build Information

Successful build of Telegrammer, reference 1.0.0-alpha.4.0.1 (cc49bf), with Swift 6.2 (beta) for macOS (SPM) on 18 Jun 2025 09:09:35 UTC.

Swift 6 data race errors: 0

Build Command

env DEVELOPER_DIR=/Applications/Xcode-26.0.0-Beta.app xcrun swift build --arch arm64

Build Log

 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+getMyCommands.swift:18:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
16 |      */
17 |     @discardableResult
18 |     func getMyCommands() throws -> Future<[BotCommand]> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
19 |         return try client
20 |             .request(endpoint: "getMyCommands")
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+getStickerSet.swift:34:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
32 |      */
33 |     @discardableResult
34 |     func getStickerSet(params: GetStickerSetParams) throws -> Future<StickerSet> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
35 |         let body = try httpBody(for: params)
36 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+getUpdates.swift:51:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
49 |      */
50 |     @discardableResult
51 |     func getUpdates(params: GetUpdatesParams? = nil) throws -> Future<[Update]> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
52 |         let body = try httpBody(for: params)
53 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+getUserProfilePhotos.swift:44:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
42 |      */
43 |     @discardableResult
44 |     func getUserProfilePhotos(params: GetUserProfilePhotosParams) throws -> Future<UserProfilePhotos> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
45 |         let body = try httpBody(for: params)
46 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+getWebhookInfo.swift:18:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
16 |      */
17 |     @discardableResult
18 |     func getWebhookInfo() throws -> Future<WebhookInfo> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
19 |         return try client
20 |             .request(endpoint: "getWebhookInfo")
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+kickChatMember.swift:44:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
42 |      */
43 |     @discardableResult
44 |     func kickChatMember(params: KickChatMemberParams) throws -> Future<Bool> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
45 |         let body = try httpBody(for: params)
46 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+leaveChat.swift:34:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
32 |      */
33 |     @discardableResult
34 |     func leaveChat(params: LeaveChatParams) throws -> Future<Bool> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
35 |         let body = try httpBody(for: params)
36 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+pinChatMessage.swift:44:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
42 |      */
43 |     @discardableResult
44 |     func pinChatMessage(params: PinChatMessageParams) throws -> Future<Bool> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
45 |         let body = try httpBody(for: params)
46 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+promoteChatMember.swift:79:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
77 |      */
78 |     @discardableResult
79 |     func promoteChatMember(params: PromoteChatMemberParams) throws -> Future<Bool> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
80 |         let body = try httpBody(for: params)
81 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+restrictChatMember.swift:49:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
47 |      */
48 |     @discardableResult
49 |     func restrictChatMember(params: RestrictChatMemberParams) throws -> Future<Bool> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
50 |         let body = try httpBody(for: params)
51 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendAnimation.swift:84:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
82 |      */
83 |     @discardableResult
84 |     func sendAnimation(params: SendAnimationParams) throws -> Future<Message> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
85 |         let body = try httpBody(for: params)
86 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendAudio.swift:85:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
83 |      */
84 |     @discardableResult
85 |     func sendAudio(params: SendAudioParams) throws -> Future<Message> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
86 |         let body = try httpBody(for: params)
87 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendChatAction.swift:41:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
39 |      */
40 |     @discardableResult
41 |     func sendChatAction(params: SendChatActionParams) throws -> Future<Bool> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
42 |         let body = try httpBody(for: params)
43 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendContact.swift:69:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
67 |      */
68 |     @discardableResult
69 |     func sendContact(params: SendContactParams) throws -> Future<Message> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
70 |         let body = try httpBody(for: params)
71 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendDice.swift:54:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
52 |      */
53 |     @discardableResult
54 |     func sendDice(params: SendDiceParams) throws -> Future<Message> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
55 |         let body = try httpBody(for: params)
56 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
[1124/1213] Compiling Telegrammer Bot+sendChatAction.swift
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+editMessageText.swift:64:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
62 |      */
63 |     @discardableResult
64 |     func editMessageText(params: EditMessageTextParams) throws -> Future<MessageOrBool> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
65 |         let body = try httpBody(for: params)
66 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+exportChatInviteLink.swift:34:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
32 |      */
33 |     @discardableResult
34 |     func exportChatInviteLink(params: ExportChatInviteLinkParams) throws -> Future<String> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
35 |         let body = try httpBody(for: params)
36 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+forwardMessage.swift:49:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
47 |      */
48 |     @discardableResult
49 |     func forwardMessage(params: ForwardMessageParams) throws -> Future<Message> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
50 |         let body = try httpBody(for: params)
51 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+getChat.swift:34:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
32 |      */
33 |     @discardableResult
34 |     func getChat(params: GetChatParams) throws -> Future<Chat> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
35 |         let body = try httpBody(for: params)
36 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+getChatAdministrators.swift:34:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
32 |      */
33 |     @discardableResult
34 |     func getChatAdministrators(params: GetChatAdministratorsParams) throws -> Future<[ChatMember]> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
35 |         let body = try httpBody(for: params)
36 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+getChatMember.swift:39:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
37 |      */
38 |     @discardableResult
39 |     func getChatMember(params: GetChatMemberParams) throws -> Future<ChatMember> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
40 |         let body = try httpBody(for: params)
41 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+getChatMembersCount.swift:34:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
32 |      */
33 |     @discardableResult
34 |     func getChatMembersCount(params: GetChatMembersCountParams) throws -> Future<Int> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
35 |         let body = try httpBody(for: params)
36 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+getFile.swift:34:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
32 |      */
33 |     @discardableResult
34 |     func getFile(params: GetFileParams) throws -> Future<File> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
35 |         let body = try httpBody(for: params)
36 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+getGameHighScores.swift:50:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
48 |      */
49 |     @discardableResult
50 |     func getGameHighScores(params: GetGameHighScoresParams) throws -> Future<[GameHighScore]> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
51 |         let body = try httpBody(for: params)
52 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+getMe.swift:18:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
16 |      */
17 |     @discardableResult
18 |     func getMe() throws -> Future<User> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
19 |         return try client
20 |             .request(endpoint: "getMe")
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+getMyCommands.swift:18:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
16 |      */
17 |     @discardableResult
18 |     func getMyCommands() throws -> Future<[BotCommand]> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
19 |         return try client
20 |             .request(endpoint: "getMyCommands")
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+getStickerSet.swift:34:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
32 |      */
33 |     @discardableResult
34 |     func getStickerSet(params: GetStickerSetParams) throws -> Future<StickerSet> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
35 |         let body = try httpBody(for: params)
36 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+getUpdates.swift:51:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
49 |      */
50 |     @discardableResult
51 |     func getUpdates(params: GetUpdatesParams? = nil) throws -> Future<[Update]> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
52 |         let body = try httpBody(for: params)
53 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+getUserProfilePhotos.swift:44:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
42 |      */
43 |     @discardableResult
44 |     func getUserProfilePhotos(params: GetUserProfilePhotosParams) throws -> Future<UserProfilePhotos> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
45 |         let body = try httpBody(for: params)
46 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+getWebhookInfo.swift:18:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
16 |      */
17 |     @discardableResult
18 |     func getWebhookInfo() throws -> Future<WebhookInfo> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
19 |         return try client
20 |             .request(endpoint: "getWebhookInfo")
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+kickChatMember.swift:44:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
42 |      */
43 |     @discardableResult
44 |     func kickChatMember(params: KickChatMemberParams) throws -> Future<Bool> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
45 |         let body = try httpBody(for: params)
46 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+leaveChat.swift:34:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
32 |      */
33 |     @discardableResult
34 |     func leaveChat(params: LeaveChatParams) throws -> Future<Bool> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
35 |         let body = try httpBody(for: params)
36 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+pinChatMessage.swift:44:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
42 |      */
43 |     @discardableResult
44 |     func pinChatMessage(params: PinChatMessageParams) throws -> Future<Bool> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
45 |         let body = try httpBody(for: params)
46 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+promoteChatMember.swift:79:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
77 |      */
78 |     @discardableResult
79 |     func promoteChatMember(params: PromoteChatMemberParams) throws -> Future<Bool> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
80 |         let body = try httpBody(for: params)
81 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+restrictChatMember.swift:49:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
47 |      */
48 |     @discardableResult
49 |     func restrictChatMember(params: RestrictChatMemberParams) throws -> Future<Bool> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
50 |         let body = try httpBody(for: params)
51 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendAnimation.swift:84:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
82 |      */
83 |     @discardableResult
84 |     func sendAnimation(params: SendAnimationParams) throws -> Future<Message> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
85 |         let body = try httpBody(for: params)
86 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendAudio.swift:85:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
83 |      */
84 |     @discardableResult
85 |     func sendAudio(params: SendAudioParams) throws -> Future<Message> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
86 |         let body = try httpBody(for: params)
87 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendChatAction.swift:41:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
39 |      */
40 |     @discardableResult
41 |     func sendChatAction(params: SendChatActionParams) throws -> Future<Bool> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
42 |         let body = try httpBody(for: params)
43 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendContact.swift:69:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
67 |      */
68 |     @discardableResult
69 |     func sendContact(params: SendContactParams) throws -> Future<Message> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
70 |         let body = try httpBody(for: params)
71 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendDice.swift:54:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
52 |      */
53 |     @discardableResult
54 |     func sendDice(params: SendDiceParams) throws -> Future<Message> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
55 |         let body = try httpBody(for: params)
56 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
[1125/1213] Compiling Telegrammer Bot+sendContact.swift
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+editMessageText.swift:64:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
62 |      */
63 |     @discardableResult
64 |     func editMessageText(params: EditMessageTextParams) throws -> Future<MessageOrBool> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
65 |         let body = try httpBody(for: params)
66 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+exportChatInviteLink.swift:34:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
32 |      */
33 |     @discardableResult
34 |     func exportChatInviteLink(params: ExportChatInviteLinkParams) throws -> Future<String> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
35 |         let body = try httpBody(for: params)
36 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+forwardMessage.swift:49:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
47 |      */
48 |     @discardableResult
49 |     func forwardMessage(params: ForwardMessageParams) throws -> Future<Message> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
50 |         let body = try httpBody(for: params)
51 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+getChat.swift:34:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
32 |      */
33 |     @discardableResult
34 |     func getChat(params: GetChatParams) throws -> Future<Chat> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
35 |         let body = try httpBody(for: params)
36 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+getChatAdministrators.swift:34:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
32 |      */
33 |     @discardableResult
34 |     func getChatAdministrators(params: GetChatAdministratorsParams) throws -> Future<[ChatMember]> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
35 |         let body = try httpBody(for: params)
36 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+getChatMember.swift:39:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
37 |      */
38 |     @discardableResult
39 |     func getChatMember(params: GetChatMemberParams) throws -> Future<ChatMember> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
40 |         let body = try httpBody(for: params)
41 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+getChatMembersCount.swift:34:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
32 |      */
33 |     @discardableResult
34 |     func getChatMembersCount(params: GetChatMembersCountParams) throws -> Future<Int> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
35 |         let body = try httpBody(for: params)
36 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+getFile.swift:34:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
32 |      */
33 |     @discardableResult
34 |     func getFile(params: GetFileParams) throws -> Future<File> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
35 |         let body = try httpBody(for: params)
36 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+getGameHighScores.swift:50:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
48 |      */
49 |     @discardableResult
50 |     func getGameHighScores(params: GetGameHighScoresParams) throws -> Future<[GameHighScore]> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
51 |         let body = try httpBody(for: params)
52 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+getMe.swift:18:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
16 |      */
17 |     @discardableResult
18 |     func getMe() throws -> Future<User> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
19 |         return try client
20 |             .request(endpoint: "getMe")
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+getMyCommands.swift:18:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
16 |      */
17 |     @discardableResult
18 |     func getMyCommands() throws -> Future<[BotCommand]> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
19 |         return try client
20 |             .request(endpoint: "getMyCommands")
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+getStickerSet.swift:34:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
32 |      */
33 |     @discardableResult
34 |     func getStickerSet(params: GetStickerSetParams) throws -> Future<StickerSet> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
35 |         let body = try httpBody(for: params)
36 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+getUpdates.swift:51:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
49 |      */
50 |     @discardableResult
51 |     func getUpdates(params: GetUpdatesParams? = nil) throws -> Future<[Update]> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
52 |         let body = try httpBody(for: params)
53 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+getUserProfilePhotos.swift:44:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
42 |      */
43 |     @discardableResult
44 |     func getUserProfilePhotos(params: GetUserProfilePhotosParams) throws -> Future<UserProfilePhotos> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
45 |         let body = try httpBody(for: params)
46 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+getWebhookInfo.swift:18:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
16 |      */
17 |     @discardableResult
18 |     func getWebhookInfo() throws -> Future<WebhookInfo> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
19 |         return try client
20 |             .request(endpoint: "getWebhookInfo")
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+kickChatMember.swift:44:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
42 |      */
43 |     @discardableResult
44 |     func kickChatMember(params: KickChatMemberParams) throws -> Future<Bool> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
45 |         let body = try httpBody(for: params)
46 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+leaveChat.swift:34:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
32 |      */
33 |     @discardableResult
34 |     func leaveChat(params: LeaveChatParams) throws -> Future<Bool> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
35 |         let body = try httpBody(for: params)
36 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+pinChatMessage.swift:44:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
42 |      */
43 |     @discardableResult
44 |     func pinChatMessage(params: PinChatMessageParams) throws -> Future<Bool> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
45 |         let body = try httpBody(for: params)
46 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+promoteChatMember.swift:79:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
77 |      */
78 |     @discardableResult
79 |     func promoteChatMember(params: PromoteChatMemberParams) throws -> Future<Bool> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
80 |         let body = try httpBody(for: params)
81 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+restrictChatMember.swift:49:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
47 |      */
48 |     @discardableResult
49 |     func restrictChatMember(params: RestrictChatMemberParams) throws -> Future<Bool> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
50 |         let body = try httpBody(for: params)
51 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendAnimation.swift:84:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
82 |      */
83 |     @discardableResult
84 |     func sendAnimation(params: SendAnimationParams) throws -> Future<Message> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
85 |         let body = try httpBody(for: params)
86 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendAudio.swift:85:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
83 |      */
84 |     @discardableResult
85 |     func sendAudio(params: SendAudioParams) throws -> Future<Message> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
86 |         let body = try httpBody(for: params)
87 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendChatAction.swift:41:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
39 |      */
40 |     @discardableResult
41 |     func sendChatAction(params: SendChatActionParams) throws -> Future<Bool> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
42 |         let body = try httpBody(for: params)
43 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendContact.swift:69:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
67 |      */
68 |     @discardableResult
69 |     func sendContact(params: SendContactParams) throws -> Future<Message> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
70 |         let body = try httpBody(for: params)
71 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendDice.swift:54:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
52 |      */
53 |     @discardableResult
54 |     func sendDice(params: SendDiceParams) throws -> Future<Message> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
55 |         let body = try httpBody(for: params)
56 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
[1126/1213] Compiling Telegrammer Bot+sendDice.swift
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+editMessageText.swift:64:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
62 |      */
63 |     @discardableResult
64 |     func editMessageText(params: EditMessageTextParams) throws -> Future<MessageOrBool> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
65 |         let body = try httpBody(for: params)
66 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+exportChatInviteLink.swift:34:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
32 |      */
33 |     @discardableResult
34 |     func exportChatInviteLink(params: ExportChatInviteLinkParams) throws -> Future<String> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
35 |         let body = try httpBody(for: params)
36 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+forwardMessage.swift:49:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
47 |      */
48 |     @discardableResult
49 |     func forwardMessage(params: ForwardMessageParams) throws -> Future<Message> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
50 |         let body = try httpBody(for: params)
51 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+getChat.swift:34:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
32 |      */
33 |     @discardableResult
34 |     func getChat(params: GetChatParams) throws -> Future<Chat> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
35 |         let body = try httpBody(for: params)
36 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+getChatAdministrators.swift:34:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
32 |      */
33 |     @discardableResult
34 |     func getChatAdministrators(params: GetChatAdministratorsParams) throws -> Future<[ChatMember]> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
35 |         let body = try httpBody(for: params)
36 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+getChatMember.swift:39:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
37 |      */
38 |     @discardableResult
39 |     func getChatMember(params: GetChatMemberParams) throws -> Future<ChatMember> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
40 |         let body = try httpBody(for: params)
41 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+getChatMembersCount.swift:34:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
32 |      */
33 |     @discardableResult
34 |     func getChatMembersCount(params: GetChatMembersCountParams) throws -> Future<Int> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
35 |         let body = try httpBody(for: params)
36 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+getFile.swift:34:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
32 |      */
33 |     @discardableResult
34 |     func getFile(params: GetFileParams) throws -> Future<File> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
35 |         let body = try httpBody(for: params)
36 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+getGameHighScores.swift:50:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
48 |      */
49 |     @discardableResult
50 |     func getGameHighScores(params: GetGameHighScoresParams) throws -> Future<[GameHighScore]> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
51 |         let body = try httpBody(for: params)
52 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+getMe.swift:18:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
16 |      */
17 |     @discardableResult
18 |     func getMe() throws -> Future<User> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
19 |         return try client
20 |             .request(endpoint: "getMe")
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+getMyCommands.swift:18:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
16 |      */
17 |     @discardableResult
18 |     func getMyCommands() throws -> Future<[BotCommand]> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
19 |         return try client
20 |             .request(endpoint: "getMyCommands")
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+getStickerSet.swift:34:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
32 |      */
33 |     @discardableResult
34 |     func getStickerSet(params: GetStickerSetParams) throws -> Future<StickerSet> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
35 |         let body = try httpBody(for: params)
36 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+getUpdates.swift:51:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
49 |      */
50 |     @discardableResult
51 |     func getUpdates(params: GetUpdatesParams? = nil) throws -> Future<[Update]> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
52 |         let body = try httpBody(for: params)
53 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+getUserProfilePhotos.swift:44:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
42 |      */
43 |     @discardableResult
44 |     func getUserProfilePhotos(params: GetUserProfilePhotosParams) throws -> Future<UserProfilePhotos> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
45 |         let body = try httpBody(for: params)
46 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+getWebhookInfo.swift:18:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
16 |      */
17 |     @discardableResult
18 |     func getWebhookInfo() throws -> Future<WebhookInfo> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
19 |         return try client
20 |             .request(endpoint: "getWebhookInfo")
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+kickChatMember.swift:44:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
42 |      */
43 |     @discardableResult
44 |     func kickChatMember(params: KickChatMemberParams) throws -> Future<Bool> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
45 |         let body = try httpBody(for: params)
46 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+leaveChat.swift:34:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
32 |      */
33 |     @discardableResult
34 |     func leaveChat(params: LeaveChatParams) throws -> Future<Bool> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
35 |         let body = try httpBody(for: params)
36 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+pinChatMessage.swift:44:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
42 |      */
43 |     @discardableResult
44 |     func pinChatMessage(params: PinChatMessageParams) throws -> Future<Bool> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
45 |         let body = try httpBody(for: params)
46 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+promoteChatMember.swift:79:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
77 |      */
78 |     @discardableResult
79 |     func promoteChatMember(params: PromoteChatMemberParams) throws -> Future<Bool> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
80 |         let body = try httpBody(for: params)
81 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+restrictChatMember.swift:49:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
47 |      */
48 |     @discardableResult
49 |     func restrictChatMember(params: RestrictChatMemberParams) throws -> Future<Bool> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
50 |         let body = try httpBody(for: params)
51 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendAnimation.swift:84:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
82 |      */
83 |     @discardableResult
84 |     func sendAnimation(params: SendAnimationParams) throws -> Future<Message> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
85 |         let body = try httpBody(for: params)
86 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendAudio.swift:85:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
83 |      */
84 |     @discardableResult
85 |     func sendAudio(params: SendAudioParams) throws -> Future<Message> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
86 |         let body = try httpBody(for: params)
87 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendChatAction.swift:41:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
39 |      */
40 |     @discardableResult
41 |     func sendChatAction(params: SendChatActionParams) throws -> Future<Bool> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
42 |         let body = try httpBody(for: params)
43 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendContact.swift:69:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
67 |      */
68 |     @discardableResult
69 |     func sendContact(params: SendContactParams) throws -> Future<Message> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
70 |         let body = try httpBody(for: params)
71 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendDice.swift:54:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
52 |      */
53 |     @discardableResult
54 |     func sendDice(params: SendDiceParams) throws -> Future<Message> {
   |          `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
55 |         let body = try httpBody(for: params)
56 |         let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:406:20: note: generic class declared here
 404 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
 405 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
 406 | public final class EventLoopFuture<Value> {
     |                    `- note: generic class declared here
 407 |     // TODO: Provide a tracing facility.  It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error.  That would simplify some debugging scenarios.
 408 |     @usableFromInline
[1127/1213] Compiling Telegrammer InlineKeyboardMarkup.swift
[1128/1213] Compiling Telegrammer InlineQuery.swift
[1129/1213] Compiling Telegrammer InlineQueryResultArticle.swift
[1130/1213] Compiling Telegrammer InlineQueryResultAudio.swift
[1131/1213] Compiling Telegrammer InlineQueryResultCachedAudio.swift
[1132/1213] Compiling Telegrammer InlineQueryResultCachedDocument.swift
[1133/1213] Compiling Telegrammer InlineQueryResultCachedGif.swift
[1134/1213] Compiling Telegrammer InlineQueryResultCachedMpeg4Gif.swift
[1135/1213] Compiling Telegrammer InlineQueryResultCachedPhoto.swift
[1136/1213] Compiling Telegrammer InlineQueryResultCachedSticker.swift
[1137/1213] Compiling Telegrammer InlineQueryResultCachedVideo.swift
[1138/1213] Compiling Telegrammer InlineQueryResultCachedVoice.swift
[1139/1213] Compiling Telegrammer InlineQueryResultContact.swift
[1140/1213] Compiling Telegrammer InlineQueryResultDocument.swift
[1141/1213] Compiling Telegrammer InlineQueryResultGame.swift
[1142/1213] Compiling Telegrammer InlineQueryResultGif.swift
[1143/1213] Compiling Telegrammer InlineQueryResultLocation.swift
[1144/1213] Compiling Telegrammer InlineQueryResultMpeg4Gif.swift
[1145/1213] Compiling Telegrammer InlineQueryResultPhoto.swift
[1146/1213] Compiling Telegrammer InlineQueryResultVenue.swift
[1147/1213] Compiling Telegrammer InlineQueryResultVideo.swift
[1148/1213] Compiling Telegrammer InlineQueryResultVoice.swift
[1149/1213] Compiling Telegrammer InputContactMessageContent.swift
[1150/1213] Compiling Telegrammer InputLocationMessageContent.swift
[1151/1213] Compiling Telegrammer RegexpFilter.swift
[1152/1213] Compiling Telegrammer ReplyFilter.swift
[1153/1213] Compiling Telegrammer StatusUpdateFilters.swift
[1154/1213] Compiling Telegrammer StickerFilter.swift
[1155/1213] Compiling Telegrammer SuccesfulPaymentFilter.swift
[1156/1213] Compiling Telegrammer TextFilter.swift
[1157/1213] Compiling Telegrammer UserFilter.swift
[1158/1213] Compiling Telegrammer VenueFilter.swift
[1159/1213] Compiling Telegrammer VideoFilter.swift
[1160/1213] Compiling Telegrammer VideoNoteFilter.swift
[1161/1213] Compiling Telegrammer VoiceFilter.swift
[1162/1213] Compiling Telegrammer CallbackQueryHandler.swift
[1163/1213] Compiling Telegrammer CommandHandler.swift
[1164/1213] Compiling Telegrammer ConversationHandler.swift
[1165/1213] Compiling Telegrammer Handler.swift
[1166/1213] Compiling Telegrammer LoggerHandler.swift
[1167/1213] Compiling Telegrammer MessageHandler.swift
[1168/1213] Compiling Telegrammer RegexpHandler.swift
[1169/1213] Compiling Telegrammer Constants.swift
[1170/1213] Compiling Telegrammer Enviroment+Helper.swift
[1171/1213] Compiling Telegrammer Error+Helpers.swift
[1172/1213] Compiling Telegrammer HTTPHeader+Helper.swift
[1173/1213] Compiling Telegrammer HTTPRequest+Helper.swift
[1174/1213] Compiling Telegrammer MultipartPartConvertible+Helper.swift
[1175/1213] Compiling Telegrammer String+Helper.swift
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Helpers/SynchronizedArray.swift:390:42: warning: capture of non-sendable type 'Element.Type' in an isolated closure
388 |     func remove(_ element: Element, completion: (() -> Void)? = nil) {
389 |         queue.async(flags: .barrier) {
390 |             guard let index = self.array.firstIndex(of: element) else { return }
    |                                          `- warning: capture of non-sendable type 'Element.Type' in an isolated closure
391 |             self.array.remove(at: index)
392 |             DispatchQueue.main.async { completion?() }
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Helpers/SynchronizedArray.swift:388:10: warning: capture of non-sendable type 'Element.Type' in an isolated closure
386 |     ///
387 |     /// - Parameter element: An element to search for in the collection.
388 |     func remove(_ element: Element, completion: (() -> Void)? = nil) {
    |          `- warning: capture of non-sendable type 'Element.Type' in an isolated closure
389 |         queue.async(flags: .barrier) {
390 |             guard let index = self.array.firstIndex(of: element) else { return }
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Network/BotClient.swift:71:33: warning: capture of non-sendable type 'T.Type' in an isolated closure
69 |             .execute(request: request)
70 |             .flatMapThrowing({ (response) -> TelegramContainer<T> in
71 |                 return try self.decode(response: response)
   |                                 `- warning: capture of non-sendable type 'T.Type' in an isolated closure
72 |             })
73 |     }
[1176/1213] Compiling Telegrammer SynchronizedArray.swift
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Helpers/SynchronizedArray.swift:390:42: warning: capture of non-sendable type 'Element.Type' in an isolated closure
388 |     func remove(_ element: Element, completion: (() -> Void)? = nil) {
389 |         queue.async(flags: .barrier) {
390 |             guard let index = self.array.firstIndex(of: element) else { return }
    |                                          `- warning: capture of non-sendable type 'Element.Type' in an isolated closure
391 |             self.array.remove(at: index)
392 |             DispatchQueue.main.async { completion?() }
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Helpers/SynchronizedArray.swift:388:10: warning: capture of non-sendable type 'Element.Type' in an isolated closure
386 |     ///
387 |     /// - Parameter element: An element to search for in the collection.
388 |     func remove(_ element: Element, completion: (() -> Void)? = nil) {
    |          `- warning: capture of non-sendable type 'Element.Type' in an isolated closure
389 |         queue.async(flags: .barrier) {
390 |             guard let index = self.array.firstIndex(of: element) else { return }
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Network/BotClient.swift:71:33: warning: capture of non-sendable type 'T.Type' in an isolated closure
69 |             .execute(request: request)
70 |             .flatMapThrowing({ (response) -> TelegramContainer<T> in
71 |                 return try self.decode(response: response)
   |                                 `- warning: capture of non-sendable type 'T.Type' in an isolated closure
72 |             })
73 |     }
[1177/1213] Compiling Telegrammer TimeAmount+Helpers.swift
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Helpers/SynchronizedArray.swift:390:42: warning: capture of non-sendable type 'Element.Type' in an isolated closure
388 |     func remove(_ element: Element, completion: (() -> Void)? = nil) {
389 |         queue.async(flags: .barrier) {
390 |             guard let index = self.array.firstIndex(of: element) else { return }
    |                                          `- warning: capture of non-sendable type 'Element.Type' in an isolated closure
391 |             self.array.remove(at: index)
392 |             DispatchQueue.main.async { completion?() }
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Helpers/SynchronizedArray.swift:388:10: warning: capture of non-sendable type 'Element.Type' in an isolated closure
386 |     ///
387 |     /// - Parameter element: An element to search for in the collection.
388 |     func remove(_ element: Element, completion: (() -> Void)? = nil) {
    |          `- warning: capture of non-sendable type 'Element.Type' in an isolated closure
389 |         queue.async(flags: .barrier) {
390 |             guard let index = self.array.firstIndex(of: element) else { return }
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Network/BotClient.swift:71:33: warning: capture of non-sendable type 'T.Type' in an isolated closure
69 |             .execute(request: request)
70 |             .flatMapThrowing({ (response) -> TelegramContainer<T> in
71 |                 return try self.decode(response: response)
   |                                 `- warning: capture of non-sendable type 'T.Type' in an isolated closure
72 |             })
73 |     }
[1178/1213] Compiling Telegrammer Bot.Settings+Proxy.swift
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Helpers/SynchronizedArray.swift:390:42: warning: capture of non-sendable type 'Element.Type' in an isolated closure
388 |     func remove(_ element: Element, completion: (() -> Void)? = nil) {
389 |         queue.async(flags: .barrier) {
390 |             guard let index = self.array.firstIndex(of: element) else { return }
    |                                          `- warning: capture of non-sendable type 'Element.Type' in an isolated closure
391 |             self.array.remove(at: index)
392 |             DispatchQueue.main.async { completion?() }
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Helpers/SynchronizedArray.swift:388:10: warning: capture of non-sendable type 'Element.Type' in an isolated closure
386 |     ///
387 |     /// - Parameter element: An element to search for in the collection.
388 |     func remove(_ element: Element, completion: (() -> Void)? = nil) {
    |          `- warning: capture of non-sendable type 'Element.Type' in an isolated closure
389 |         queue.async(flags: .barrier) {
390 |             guard let index = self.array.firstIndex(of: element) else { return }
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Network/BotClient.swift:71:33: warning: capture of non-sendable type 'T.Type' in an isolated closure
69 |             .execute(request: request)
70 |             .flatMapThrowing({ (response) -> TelegramContainer<T> in
71 |                 return try self.decode(response: response)
   |                                 `- warning: capture of non-sendable type 'T.Type' in an isolated closure
72 |             })
73 |     }
[1179/1213] Compiling Telegrammer BotClient.swift
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Helpers/SynchronizedArray.swift:390:42: warning: capture of non-sendable type 'Element.Type' in an isolated closure
388 |     func remove(_ element: Element, completion: (() -> Void)? = nil) {
389 |         queue.async(flags: .barrier) {
390 |             guard let index = self.array.firstIndex(of: element) else { return }
    |                                          `- warning: capture of non-sendable type 'Element.Type' in an isolated closure
391 |             self.array.remove(at: index)
392 |             DispatchQueue.main.async { completion?() }
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Helpers/SynchronizedArray.swift:388:10: warning: capture of non-sendable type 'Element.Type' in an isolated closure
386 |     ///
387 |     /// - Parameter element: An element to search for in the collection.
388 |     func remove(_ element: Element, completion: (() -> Void)? = nil) {
    |          `- warning: capture of non-sendable type 'Element.Type' in an isolated closure
389 |         queue.async(flags: .barrier) {
390 |             guard let index = self.array.firstIndex(of: element) else { return }
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Network/BotClient.swift:71:33: warning: capture of non-sendable type 'T.Type' in an isolated closure
69 |             .execute(request: request)
70 |             .flatMapThrowing({ (response) -> TelegramContainer<T> in
71 |                 return try self.decode(response: response)
   |                                 `- warning: capture of non-sendable type 'T.Type' in an isolated closure
72 |             })
73 |     }
[1180/1213] Compiling Telegrammer Longpolling.swift
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Helpers/SynchronizedArray.swift:390:42: warning: capture of non-sendable type 'Element.Type' in an isolated closure
388 |     func remove(_ element: Element, completion: (() -> Void)? = nil) {
389 |         queue.async(flags: .barrier) {
390 |             guard let index = self.array.firstIndex(of: element) else { return }
    |                                          `- warning: capture of non-sendable type 'Element.Type' in an isolated closure
391 |             self.array.remove(at: index)
392 |             DispatchQueue.main.async { completion?() }
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Helpers/SynchronizedArray.swift:388:10: warning: capture of non-sendable type 'Element.Type' in an isolated closure
386 |     ///
387 |     /// - Parameter element: An element to search for in the collection.
388 |     func remove(_ element: Element, completion: (() -> Void)? = nil) {
    |          `- warning: capture of non-sendable type 'Element.Type' in an isolated closure
389 |         queue.async(flags: .barrier) {
390 |             guard let index = self.array.firstIndex(of: element) else { return }
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Network/BotClient.swift:71:33: warning: capture of non-sendable type 'T.Type' in an isolated closure
69 |             .execute(request: request)
70 |             .flatMapThrowing({ (response) -> TelegramContainer<T> in
71 |                 return try self.decode(response: response)
   |                                 `- warning: capture of non-sendable type 'T.Type' in an isolated closure
72 |             })
73 |     }
[1181/1213] Compiling Telegrammer Network.swift
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Helpers/SynchronizedArray.swift:390:42: warning: capture of non-sendable type 'Element.Type' in an isolated closure
388 |     func remove(_ element: Element, completion: (() -> Void)? = nil) {
389 |         queue.async(flags: .barrier) {
390 |             guard let index = self.array.firstIndex(of: element) else { return }
    |                                          `- warning: capture of non-sendable type 'Element.Type' in an isolated closure
391 |             self.array.remove(at: index)
392 |             DispatchQueue.main.async { completion?() }
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Helpers/SynchronizedArray.swift:388:10: warning: capture of non-sendable type 'Element.Type' in an isolated closure
386 |     ///
387 |     /// - Parameter element: An element to search for in the collection.
388 |     func remove(_ element: Element, completion: (() -> Void)? = nil) {
    |          `- warning: capture of non-sendable type 'Element.Type' in an isolated closure
389 |         queue.async(flags: .barrier) {
390 |             guard let index = self.array.firstIndex(of: element) else { return }
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Network/BotClient.swift:71:33: warning: capture of non-sendable type 'T.Type' in an isolated closure
69 |             .execute(request: request)
70 |             .flatMapThrowing({ (response) -> TelegramContainer<T> in
71 |                 return try self.decode(response: response)
   |                                 `- warning: capture of non-sendable type 'T.Type' in an isolated closure
72 |             })
73 |     }
[1182/1213] Compiling Telegrammer UpdatesServer.swift
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Helpers/SynchronizedArray.swift:390:42: warning: capture of non-sendable type 'Element.Type' in an isolated closure
388 |     func remove(_ element: Element, completion: (() -> Void)? = nil) {
389 |         queue.async(flags: .barrier) {
390 |             guard let index = self.array.firstIndex(of: element) else { return }
    |                                          `- warning: capture of non-sendable type 'Element.Type' in an isolated closure
391 |             self.array.remove(at: index)
392 |             DispatchQueue.main.async { completion?() }
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Helpers/SynchronizedArray.swift:388:10: warning: capture of non-sendable type 'Element.Type' in an isolated closure
386 |     ///
387 |     /// - Parameter element: An element to search for in the collection.
388 |     func remove(_ element: Element, completion: (() -> Void)? = nil) {
    |          `- warning: capture of non-sendable type 'Element.Type' in an isolated closure
389 |         queue.async(flags: .barrier) {
390 |             guard let index = self.array.firstIndex(of: element) else { return }
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Network/BotClient.swift:71:33: warning: capture of non-sendable type 'T.Type' in an isolated closure
69 |             .execute(request: request)
70 |             .flatMapThrowing({ (response) -> TelegramContainer<T> in
71 |                 return try self.decode(response: response)
   |                                 `- warning: capture of non-sendable type 'T.Type' in an isolated closure
72 |             })
73 |     }
[1183/1213] Compiling Telegrammer Webhooks.swift
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Helpers/SynchronizedArray.swift:390:42: warning: capture of non-sendable type 'Element.Type' in an isolated closure
388 |     func remove(_ element: Element, completion: (() -> Void)? = nil) {
389 |         queue.async(flags: .barrier) {
390 |             guard let index = self.array.firstIndex(of: element) else { return }
    |                                          `- warning: capture of non-sendable type 'Element.Type' in an isolated closure
391 |             self.array.remove(at: index)
392 |             DispatchQueue.main.async { completion?() }
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Helpers/SynchronizedArray.swift:388:10: warning: capture of non-sendable type 'Element.Type' in an isolated closure
386 |     ///
387 |     /// - Parameter element: An element to search for in the collection.
388 |     func remove(_ element: Element, completion: (() -> Void)? = nil) {
    |          `- warning: capture of non-sendable type 'Element.Type' in an isolated closure
389 |         queue.async(flags: .barrier) {
390 |             guard let index = self.array.firstIndex(of: element) else { return }
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Network/BotClient.swift:71:33: warning: capture of non-sendable type 'T.Type' in an isolated closure
69 |             .execute(request: request)
70 |             .flatMapThrowing({ (response) -> TelegramContainer<T> in
71 |                 return try self.decode(response: response)
   |                                 `- warning: capture of non-sendable type 'T.Type' in an isolated closure
72 |             })
73 |     }
[1184/1213] Compiling Telegrammer ChatId.swift
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Helpers/SynchronizedArray.swift:390:42: warning: capture of non-sendable type 'Element.Type' in an isolated closure
388 |     func remove(_ element: Element, completion: (() -> Void)? = nil) {
389 |         queue.async(flags: .barrier) {
390 |             guard let index = self.array.firstIndex(of: element) else { return }
    |                                          `- warning: capture of non-sendable type 'Element.Type' in an isolated closure
391 |             self.array.remove(at: index)
392 |             DispatchQueue.main.async { completion?() }
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Helpers/SynchronizedArray.swift:388:10: warning: capture of non-sendable type 'Element.Type' in an isolated closure
386 |     ///
387 |     /// - Parameter element: An element to search for in the collection.
388 |     func remove(_ element: Element, completion: (() -> Void)? = nil) {
    |          `- warning: capture of non-sendable type 'Element.Type' in an isolated closure
389 |         queue.async(flags: .barrier) {
390 |             guard let index = self.array.firstIndex(of: element) else { return }
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Network/BotClient.swift:71:33: warning: capture of non-sendable type 'T.Type' in an isolated closure
69 |             .execute(request: request)
70 |             .flatMapThrowing({ (response) -> TelegramContainer<T> in
71 |                 return try self.decode(response: response)
   |                                 `- warning: capture of non-sendable type 'T.Type' in an isolated closure
72 |             })
73 |     }
[1185/1213] Compiling Telegrammer ChatType.swift
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Helpers/SynchronizedArray.swift:390:42: warning: capture of non-sendable type 'Element.Type' in an isolated closure
388 |     func remove(_ element: Element, completion: (() -> Void)? = nil) {
389 |         queue.async(flags: .barrier) {
390 |             guard let index = self.array.firstIndex(of: element) else { return }
    |                                          `- warning: capture of non-sendable type 'Element.Type' in an isolated closure
391 |             self.array.remove(at: index)
392 |             DispatchQueue.main.async { completion?() }
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Helpers/SynchronizedArray.swift:388:10: warning: capture of non-sendable type 'Element.Type' in an isolated closure
386 |     ///
387 |     /// - Parameter element: An element to search for in the collection.
388 |     func remove(_ element: Element, completion: (() -> Void)? = nil) {
    |          `- warning: capture of non-sendable type 'Element.Type' in an isolated closure
389 |         queue.async(flags: .barrier) {
390 |             guard let index = self.array.firstIndex(of: element) else { return }
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Network/BotClient.swift:71:33: warning: capture of non-sendable type 'T.Type' in an isolated closure
69 |             .execute(request: request)
70 |             .flatMapThrowing({ (response) -> TelegramContainer<T> in
71 |                 return try self.decode(response: response)
   |                                 `- warning: capture of non-sendable type 'T.Type' in an isolated closure
72 |             })
73 |     }
[1186/1213] Compiling Telegrammer FileInfo.swift
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Helpers/SynchronizedArray.swift:390:42: warning: capture of non-sendable type 'Element.Type' in an isolated closure
388 |     func remove(_ element: Element, completion: (() -> Void)? = nil) {
389 |         queue.async(flags: .barrier) {
390 |             guard let index = self.array.firstIndex(of: element) else { return }
    |                                          `- warning: capture of non-sendable type 'Element.Type' in an isolated closure
391 |             self.array.remove(at: index)
392 |             DispatchQueue.main.async { completion?() }
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Helpers/SynchronizedArray.swift:388:10: warning: capture of non-sendable type 'Element.Type' in an isolated closure
386 |     ///
387 |     /// - Parameter element: An element to search for in the collection.
388 |     func remove(_ element: Element, completion: (() -> Void)? = nil) {
    |          `- warning: capture of non-sendable type 'Element.Type' in an isolated closure
389 |         queue.async(flags: .barrier) {
390 |             guard let index = self.array.firstIndex(of: element) else { return }
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Network/BotClient.swift:71:33: warning: capture of non-sendable type 'T.Type' in an isolated closure
69 |             .execute(request: request)
70 |             .flatMapThrowing({ (response) -> TelegramContainer<T> in
71 |                 return try self.decode(response: response)
   |                                 `- warning: capture of non-sendable type 'T.Type' in an isolated closure
72 |             })
73 |     }
[1187/1213] Compiling Telegrammer InlineQueryResult.swift
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Helpers/SynchronizedArray.swift:390:42: warning: capture of non-sendable type 'Element.Type' in an isolated closure
388 |     func remove(_ element: Element, completion: (() -> Void)? = nil) {
389 |         queue.async(flags: .barrier) {
390 |             guard let index = self.array.firstIndex(of: element) else { return }
    |                                          `- warning: capture of non-sendable type 'Element.Type' in an isolated closure
391 |             self.array.remove(at: index)
392 |             DispatchQueue.main.async { completion?() }
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Helpers/SynchronizedArray.swift:388:10: warning: capture of non-sendable type 'Element.Type' in an isolated closure
386 |     ///
387 |     /// - Parameter element: An element to search for in the collection.
388 |     func remove(_ element: Element, completion: (() -> Void)? = nil) {
    |          `- warning: capture of non-sendable type 'Element.Type' in an isolated closure
389 |         queue.async(flags: .barrier) {
390 |             guard let index = self.array.firstIndex(of: element) else { return }
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Network/BotClient.swift:71:33: warning: capture of non-sendable type 'T.Type' in an isolated closure
69 |             .execute(request: request)
70 |             .flatMapThrowing({ (response) -> TelegramContainer<T> in
71 |                 return try self.decode(response: response)
   |                                 `- warning: capture of non-sendable type 'T.Type' in an isolated closure
72 |             })
73 |     }
[1188/1213] Compiling Telegrammer InputFile.swift
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Helpers/SynchronizedArray.swift:390:42: warning: capture of non-sendable type 'Element.Type' in an isolated closure
388 |     func remove(_ element: Element, completion: (() -> Void)? = nil) {
389 |         queue.async(flags: .barrier) {
390 |             guard let index = self.array.firstIndex(of: element) else { return }
    |                                          `- warning: capture of non-sendable type 'Element.Type' in an isolated closure
391 |             self.array.remove(at: index)
392 |             DispatchQueue.main.async { completion?() }
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Helpers/SynchronizedArray.swift:388:10: warning: capture of non-sendable type 'Element.Type' in an isolated closure
386 |     ///
387 |     /// - Parameter element: An element to search for in the collection.
388 |     func remove(_ element: Element, completion: (() -> Void)? = nil) {
    |          `- warning: capture of non-sendable type 'Element.Type' in an isolated closure
389 |         queue.async(flags: .barrier) {
390 |             guard let index = self.array.firstIndex(of: element) else { return }
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Network/BotClient.swift:71:33: warning: capture of non-sendable type 'T.Type' in an isolated closure
69 |             .execute(request: request)
70 |             .flatMapThrowing({ (response) -> TelegramContainer<T> in
71 |                 return try self.decode(response: response)
   |                                 `- warning: capture of non-sendable type 'T.Type' in an isolated closure
72 |             })
73 |     }
[1189/1213] Compiling Telegrammer InputMedia.swift
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Helpers/SynchronizedArray.swift:390:42: warning: capture of non-sendable type 'Element.Type' in an isolated closure
388 |     func remove(_ element: Element, completion: (() -> Void)? = nil) {
389 |         queue.async(flags: .barrier) {
390 |             guard let index = self.array.firstIndex(of: element) else { return }
    |                                          `- warning: capture of non-sendable type 'Element.Type' in an isolated closure
391 |             self.array.remove(at: index)
392 |             DispatchQueue.main.async { completion?() }
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Helpers/SynchronizedArray.swift:388:10: warning: capture of non-sendable type 'Element.Type' in an isolated closure
386 |     ///
387 |     /// - Parameter element: An element to search for in the collection.
388 |     func remove(_ element: Element, completion: (() -> Void)? = nil) {
    |          `- warning: capture of non-sendable type 'Element.Type' in an isolated closure
389 |         queue.async(flags: .barrier) {
390 |             guard let index = self.array.firstIndex(of: element) else { return }
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Network/BotClient.swift:71:33: warning: capture of non-sendable type 'T.Type' in an isolated closure
69 |             .execute(request: request)
70 |             .flatMapThrowing({ (response) -> TelegramContainer<T> in
71 |                 return try self.decode(response: response)
   |                                 `- warning: capture of non-sendable type 'T.Type' in an isolated closure
72 |             })
73 |     }
[1190/1213] Compiling Telegrammer InputMessageContent.swift
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Helpers/SynchronizedArray.swift:390:42: warning: capture of non-sendable type 'Element.Type' in an isolated closure
388 |     func remove(_ element: Element, completion: (() -> Void)? = nil) {
389 |         queue.async(flags: .barrier) {
390 |             guard let index = self.array.firstIndex(of: element) else { return }
    |                                          `- warning: capture of non-sendable type 'Element.Type' in an isolated closure
391 |             self.array.remove(at: index)
392 |             DispatchQueue.main.async { completion?() }
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Helpers/SynchronizedArray.swift:388:10: warning: capture of non-sendable type 'Element.Type' in an isolated closure
386 |     ///
387 |     /// - Parameter element: An element to search for in the collection.
388 |     func remove(_ element: Element, completion: (() -> Void)? = nil) {
    |          `- warning: capture of non-sendable type 'Element.Type' in an isolated closure
389 |         queue.async(flags: .barrier) {
390 |             guard let index = self.array.firstIndex(of: element) else { return }
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Network/BotClient.swift:71:33: warning: capture of non-sendable type 'T.Type' in an isolated closure
69 |             .execute(request: request)
70 |             .flatMapThrowing({ (response) -> TelegramContainer<T> in
71 |                 return try self.decode(response: response)
   |                                 `- warning: capture of non-sendable type 'T.Type' in an isolated closure
72 |             })
73 |     }
[1191/1213] Compiling Telegrammer MessageEntityType.swift
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Helpers/SynchronizedArray.swift:390:42: warning: capture of non-sendable type 'Element.Type' in an isolated closure
388 |     func remove(_ element: Element, completion: (() -> Void)? = nil) {
389 |         queue.async(flags: .barrier) {
390 |             guard let index = self.array.firstIndex(of: element) else { return }
    |                                          `- warning: capture of non-sendable type 'Element.Type' in an isolated closure
391 |             self.array.remove(at: index)
392 |             DispatchQueue.main.async { completion?() }
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Helpers/SynchronizedArray.swift:388:10: warning: capture of non-sendable type 'Element.Type' in an isolated closure
386 |     ///
387 |     /// - Parameter element: An element to search for in the collection.
388 |     func remove(_ element: Element, completion: (() -> Void)? = nil) {
    |          `- warning: capture of non-sendable type 'Element.Type' in an isolated closure
389 |         queue.async(flags: .barrier) {
390 |             guard let index = self.array.firstIndex(of: element) else { return }
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Network/BotClient.swift:71:33: warning: capture of non-sendable type 'T.Type' in an isolated closure
69 |             .execute(request: request)
70 |             .flatMapThrowing({ (response) -> TelegramContainer<T> in
71 |                 return try self.decode(response: response)
   |                                 `- warning: capture of non-sendable type 'T.Type' in an isolated closure
72 |             })
73 |     }
[1192/1213] Compiling Telegrammer MessageOrBool.swift
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Helpers/SynchronizedArray.swift:390:42: warning: capture of non-sendable type 'Element.Type' in an isolated closure
388 |     func remove(_ element: Element, completion: (() -> Void)? = nil) {
389 |         queue.async(flags: .barrier) {
390 |             guard let index = self.array.firstIndex(of: element) else { return }
    |                                          `- warning: capture of non-sendable type 'Element.Type' in an isolated closure
391 |             self.array.remove(at: index)
392 |             DispatchQueue.main.async { completion?() }
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Helpers/SynchronizedArray.swift:388:10: warning: capture of non-sendable type 'Element.Type' in an isolated closure
386 |     ///
387 |     /// - Parameter element: An element to search for in the collection.
388 |     func remove(_ element: Element, completion: (() -> Void)? = nil) {
    |          `- warning: capture of non-sendable type 'Element.Type' in an isolated closure
389 |         queue.async(flags: .barrier) {
390 |             guard let index = self.array.firstIndex(of: element) else { return }
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Network/BotClient.swift:71:33: warning: capture of non-sendable type 'T.Type' in an isolated closure
69 |             .execute(request: request)
70 |             .flatMapThrowing({ (response) -> TelegramContainer<T> in
71 |                 return try self.decode(response: response)
   |                                 `- warning: capture of non-sendable type 'T.Type' in an isolated closure
72 |             })
73 |     }
[1193/1213] Compiling Telegrammer ParseMode.swift
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Helpers/SynchronizedArray.swift:390:42: warning: capture of non-sendable type 'Element.Type' in an isolated closure
388 |     func remove(_ element: Element, completion: (() -> Void)? = nil) {
389 |         queue.async(flags: .barrier) {
390 |             guard let index = self.array.firstIndex(of: element) else { return }
    |                                          `- warning: capture of non-sendable type 'Element.Type' in an isolated closure
391 |             self.array.remove(at: index)
392 |             DispatchQueue.main.async { completion?() }
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Helpers/SynchronizedArray.swift:388:10: warning: capture of non-sendable type 'Element.Type' in an isolated closure
386 |     ///
387 |     /// - Parameter element: An element to search for in the collection.
388 |     func remove(_ element: Element, completion: (() -> Void)? = nil) {
    |          `- warning: capture of non-sendable type 'Element.Type' in an isolated closure
389 |         queue.async(flags: .barrier) {
390 |             guard let index = self.array.firstIndex(of: element) else { return }
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Network/BotClient.swift:71:33: warning: capture of non-sendable type 'T.Type' in an isolated closure
69 |             .execute(request: request)
70 |             .flatMapThrowing({ (response) -> TelegramContainer<T> in
71 |                 return try self.decode(response: response)
   |                                 `- warning: capture of non-sendable type 'T.Type' in an isolated closure
72 |             })
73 |     }
[1194/1213] Compiling Telegrammer PassportElementError.swift
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Helpers/SynchronizedArray.swift:390:42: warning: capture of non-sendable type 'Element.Type' in an isolated closure
388 |     func remove(_ element: Element, completion: (() -> Void)? = nil) {
389 |         queue.async(flags: .barrier) {
390 |             guard let index = self.array.firstIndex(of: element) else { return }
    |                                          `- warning: capture of non-sendable type 'Element.Type' in an isolated closure
391 |             self.array.remove(at: index)
392 |             DispatchQueue.main.async { completion?() }
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Helpers/SynchronizedArray.swift:388:10: warning: capture of non-sendable type 'Element.Type' in an isolated closure
386 |     ///
387 |     /// - Parameter element: An element to search for in the collection.
388 |     func remove(_ element: Element, completion: (() -> Void)? = nil) {
    |          `- warning: capture of non-sendable type 'Element.Type' in an isolated closure
389 |         queue.async(flags: .barrier) {
390 |             guard let index = self.array.firstIndex(of: element) else { return }
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Network/BotClient.swift:71:33: warning: capture of non-sendable type 'T.Type' in an isolated closure
69 |             .execute(request: request)
70 |             .flatMapThrowing({ (response) -> TelegramContainer<T> in
71 |                 return try self.decode(response: response)
   |                                 `- warning: capture of non-sendable type 'T.Type' in an isolated closure
72 |             })
73 |     }
[1195/1213] Compiling Telegrammer ReplyMarkup.swift
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Helpers/SynchronizedArray.swift:390:42: warning: capture of non-sendable type 'Element.Type' in an isolated closure
388 |     func remove(_ element: Element, completion: (() -> Void)? = nil) {
389 |         queue.async(flags: .barrier) {
390 |             guard let index = self.array.firstIndex(of: element) else { return }
    |                                          `- warning: capture of non-sendable type 'Element.Type' in an isolated closure
391 |             self.array.remove(at: index)
392 |             DispatchQueue.main.async { completion?() }
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Helpers/SynchronizedArray.swift:388:10: warning: capture of non-sendable type 'Element.Type' in an isolated closure
386 |     ///
387 |     /// - Parameter element: An element to search for in the collection.
388 |     func remove(_ element: Element, completion: (() -> Void)? = nil) {
    |          `- warning: capture of non-sendable type 'Element.Type' in an isolated closure
389 |         queue.async(flags: .barrier) {
390 |             guard let index = self.array.firstIndex(of: element) else { return }
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Network/BotClient.swift:71:33: warning: capture of non-sendable type 'T.Type' in an isolated closure
69 |             .execute(request: request)
70 |             .flatMapThrowing({ (response) -> TelegramContainer<T> in
71 |                 return try self.decode(response: response)
   |                                 `- warning: capture of non-sendable type 'T.Type' in an isolated closure
72 |             })
73 |     }
[1196/1213] Compiling Telegrammer TelegramContainer.swift
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Helpers/SynchronizedArray.swift:390:42: warning: capture of non-sendable type 'Element.Type' in an isolated closure
388 |     func remove(_ element: Element, completion: (() -> Void)? = nil) {
389 |         queue.async(flags: .barrier) {
390 |             guard let index = self.array.firstIndex(of: element) else { return }
    |                                          `- warning: capture of non-sendable type 'Element.Type' in an isolated closure
391 |             self.array.remove(at: index)
392 |             DispatchQueue.main.async { completion?() }
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Helpers/SynchronizedArray.swift:388:10: warning: capture of non-sendable type 'Element.Type' in an isolated closure
386 |     ///
387 |     /// - Parameter element: An element to search for in the collection.
388 |     func remove(_ element: Element, completion: (() -> Void)? = nil) {
    |          `- warning: capture of non-sendable type 'Element.Type' in an isolated closure
389 |         queue.async(flags: .barrier) {
390 |             guard let index = self.array.firstIndex(of: element) else { return }
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Network/BotClient.swift:71:33: warning: capture of non-sendable type 'T.Type' in an isolated closure
69 |             .execute(request: request)
70 |             .flatMapThrowing({ (response) -> TelegramContainer<T> in
71 |                 return try self.decode(response: response)
   |                                 `- warning: capture of non-sendable type 'T.Type' in an isolated closure
72 |             })
73 |     }
[1197/1213] Compiling Telegrammer TelegramEncodables.swift
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Helpers/SynchronizedArray.swift:390:42: warning: capture of non-sendable type 'Element.Type' in an isolated closure
388 |     func remove(_ element: Element, completion: (() -> Void)? = nil) {
389 |         queue.async(flags: .barrier) {
390 |             guard let index = self.array.firstIndex(of: element) else { return }
    |                                          `- warning: capture of non-sendable type 'Element.Type' in an isolated closure
391 |             self.array.remove(at: index)
392 |             DispatchQueue.main.async { completion?() }
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Helpers/SynchronizedArray.swift:388:10: warning: capture of non-sendable type 'Element.Type' in an isolated closure
386 |     ///
387 |     /// - Parameter element: An element to search for in the collection.
388 |     func remove(_ element: Element, completion: (() -> Void)? = nil) {
    |          `- warning: capture of non-sendable type 'Element.Type' in an isolated closure
389 |         queue.async(flags: .barrier) {
390 |             guard let index = self.array.firstIndex(of: element) else { return }
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Network/BotClient.swift:71:33: warning: capture of non-sendable type 'T.Type' in an isolated closure
69 |             .execute(request: request)
70 |             .flatMapThrowing({ (response) -> TelegramContainer<T> in
71 |                 return try self.decode(response: response)
   |                                 `- warning: capture of non-sendable type 'T.Type' in an isolated closure
72 |             })
73 |     }
[1198/1213] Compiling Telegrammer Updater.swift
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Helpers/SynchronizedArray.swift:390:42: warning: capture of non-sendable type 'Element.Type' in an isolated closure
388 |     func remove(_ element: Element, completion: (() -> Void)? = nil) {
389 |         queue.async(flags: .barrier) {
390 |             guard let index = self.array.firstIndex(of: element) else { return }
    |                                          `- warning: capture of non-sendable type 'Element.Type' in an isolated closure
391 |             self.array.remove(at: index)
392 |             DispatchQueue.main.async { completion?() }
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Helpers/SynchronizedArray.swift:388:10: warning: capture of non-sendable type 'Element.Type' in an isolated closure
386 |     ///
387 |     /// - Parameter element: An element to search for in the collection.
388 |     func remove(_ element: Element, completion: (() -> Void)? = nil) {
    |          `- warning: capture of non-sendable type 'Element.Type' in an isolated closure
389 |         queue.async(flags: .barrier) {
390 |             guard let index = self.array.firstIndex(of: element) else { return }
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Network/BotClient.swift:71:33: warning: capture of non-sendable type 'T.Type' in an isolated closure
69 |             .execute(request: request)
70 |             .flatMapThrowing({ (response) -> TelegramContainer<T> in
71 |                 return try self.decode(response: response)
   |                                 `- warning: capture of non-sendable type 'T.Type' in an isolated closure
72 |             })
73 |     }
[1199/1230] Compiling DemoWebhooksLocally main.swift
[1200/1230] Emitting module DemoWebhooksLocally
[1200/1230] Write Objects.LinkFileList
[1202/1230] Emitting module DemoHelloBot
[1203/1230] Compiling DemoHelloBot NewMemberHandler.swift
[1204/1230] Compiling DemoHelloBot main.swift
[1205/1230] Compiling DemoEchoBot main.swift
[1206/1230] Emitting module DemoEchoBot
[1207/1230] Compiling DemoSpellCheckerBot main.swift
[1208/1230] Emitting module DemoSpellCheckerBot
/Users/admin/builder/spi-builder-workspace/Sources/DemoSpellCheckerBot/SpellChecker/YaSpellChecker.swift:18:54: warning: 'createNew' is deprecated: Please use the singleton EventLoopGroup explicitly [#DeprecatedDeclaration]
16 |     var url = "https://speller.yandex.net/services/spellservice.json/checkText"
17 |
18 |     let client = HTTPClient(eventLoopGroupProvider: .createNew)
   |                                                      |- warning: 'createNew' is deprecated: Please use the singleton EventLoopGroup explicitly [#DeprecatedDeclaration]
   |                                                      `- note: use 'singleton' instead
19 |
20 |     func check(_ text: String, lang: Lang, format: Format) throws -> Future<[T]> {
[#DeprecatedDeclaration]: <https://docs.swift.org/compiler/documentation/diagnostics/deprecated-declaration>
[1209/1230] Compiling DemoSpellCheckerBot SpellCheckerController.swift
/Users/admin/builder/spi-builder-workspace/Sources/DemoSpellCheckerBot/Controllers/SpellCheckerController.swift:149:60: warning: 'markdown' is deprecated: This is a legacy mode, retained for backward compatibility. [#DeprecatedDeclaration]
147 |                                                messageId: message.messageId,
148 |                                                text: text,
149 |                                                parseMode: .markdown,
    |                                                            |- warning: 'markdown' is deprecated: This is a legacy mode, retained for backward compatibility. [#DeprecatedDeclaration]
    |                                                            `- note: use 'markdownV2' instead
150 |                                                replyMarkup: markup)
151 |         try bot.editMessageText(params: params)
/Users/admin/builder/spi-builder-workspace/Sources/DemoSpellCheckerBot/Controllers/SpellCheckerController.swift:157:56: warning: 'markdown' is deprecated: This is a legacy mode, retained for backward compatibility. [#DeprecatedDeclaration]
155 |         let params = Bot.SendMessageParams(chatId: .chat(message.chat.id),
156 |                                            text: text,
157 |                                            parseMode: .markdown,
    |                                                        |- warning: 'markdown' is deprecated: This is a legacy mode, retained for backward compatibility. [#DeprecatedDeclaration]
    |                                                        `- note: use 'markdownV2' instead
158 |                                            replyMarkup: markup)
159 |         try self.bot.sendMessage(params: params)
/Users/admin/builder/spi-builder-workspace/Sources/DemoSpellCheckerBot/SpellChecker/YaSpellChecker.swift:18:54: warning: 'createNew' is deprecated: Please use the singleton EventLoopGroup explicitly [#DeprecatedDeclaration]
16 |     var url = "https://speller.yandex.net/services/spellservice.json/checkText"
17 |
18 |     let client = HTTPClient(eventLoopGroupProvider: .createNew)
   |                                                      |- warning: 'createNew' is deprecated: Please use the singleton EventLoopGroup explicitly [#DeprecatedDeclaration]
   |                                                      `- note: use 'singleton' instead
19 |
20 |     func check(_ text: String, lang: Lang, format: Format) throws -> Future<[T]> {
[#DeprecatedDeclaration]: <https://docs.swift.org/compiler/documentation/diagnostics/deprecated-declaration>
[1210/1230] Emitting module DemoSchedulerBot
[1211/1230] Compiling DemoSchedulerBot main.swift
[1212/1230] Compiling DemoSpellCheckerBot YaSpellChecker.swift
/Users/admin/builder/spi-builder-workspace/Sources/DemoSpellCheckerBot/SpellChecker/YaSpellChecker.swift:18:54: warning: 'createNew' is deprecated: Please use the singleton EventLoopGroup explicitly [#DeprecatedDeclaration]
16 |     var url = "https://speller.yandex.net/services/spellservice.json/checkText"
17 |
18 |     let client = HTTPClient(eventLoopGroupProvider: .createNew)
   |                                                      |- warning: 'createNew' is deprecated: Please use the singleton EventLoopGroup explicitly [#DeprecatedDeclaration]
   |                                                      `- note: use 'singleton' instead
19 |
20 |     func check(_ text: String, lang: Lang, format: Format) throws -> Future<[T]> {
[#DeprecatedDeclaration]: <https://docs.swift.org/compiler/documentation/diagnostics/deprecated-declaration>
[1213/1230] Compiling DemoSpellCheckerBot SpellChecker.swift
[1214/1230] Compiling DemoSpellCheckerBot Array+Helper.swift
[1215/1230] Compiling DemoSpellCheckerBot YaSpellCheck.swift
[1216/1230] Compiling DemoSpellCheckerBot YaSpellFlow.swift
[1216/1230] Write Objects.LinkFileList
[1220/1230] Linking HelloBot
[1220/1230] Linking EchoBot
[1222/1230] Linking SpellCheckerBot
[1223/1230] Linking WebhooksLocally
[1223/1230] Linking SchedulerBot
[1225/1230] Applying WebhooksLocally
[1225/1230] Applying EchoBot
[1227/1230] Applying HelloBot
[1228/1230] Applying SchedulerBot
[1229/1230] Applying SpellCheckerBot
Build complete! (71.51s)
Fetching https://github.com/apple/swift-log.git
Fetching https://github.com/apple/swift-nio.git
Fetching https://github.com/swift-server/async-http-client.git
[1/3836] Fetching swift-log
[1152/17850] Fetching swift-log, async-http-client
[4959/94177] Fetching swift-log, async-http-client, swift-nio
Fetched https://github.com/swift-server/async-http-client.git from cache (4.09s)
Fetched https://github.com/apple/swift-log.git from cache (4.09s)
Fetched https://github.com/apple/swift-nio.git from cache (4.09s)
Computing version for https://github.com/apple/swift-log.git
Computed https://github.com/apple/swift-log.git at 1.6.3 (4.55s)
Computing version for https://github.com/swift-server/async-http-client.git
Computed https://github.com/swift-server/async-http-client.git at 1.26.1 (0.43s)
Fetching https://github.com/apple/swift-nio-http2.git
Fetching https://github.com/apple/swift-nio-extras.git
Fetching https://github.com/apple/swift-algorithms.git
Fetching https://github.com/apple/swift-atomics.git
Fetching https://github.com/apple/swift-nio-transport-services.git
Fetching https://github.com/apple/swift-nio-ssl.git
[1/5959] Fetching swift-algorithms
[61/8626] Fetching swift-algorithms, swift-nio-transport-services
[255/20158] Fetching swift-algorithms, swift-nio-transport-services, swift-nio-http2
[256/21955] Fetching swift-algorithms, swift-nio-transport-services, swift-nio-http2, swift-atomics
[470/27878] Fetching swift-algorithms, swift-nio-transport-services, swift-nio-http2, swift-atomics, swift-nio-extras
[9853/42768] Fetching swift-algorithms, swift-nio-transport-services, swift-nio-http2, swift-atomics, swift-nio-extras, swift-nio-ssl
Fetched https://github.com/apple/swift-nio-extras.git from cache (1.38s)
[17020/36845] Fetching swift-algorithms, swift-nio-transport-services, swift-nio-http2, swift-atomics, swift-nio-ssl
Fetched https://github.com/apple/swift-atomics.git from cache (3.71s)
Fetched https://github.com/apple/swift-algorithms.git from cache (3.71s)
Fetched https://github.com/apple/swift-nio-ssl.git from cache (3.71s)
Fetched https://github.com/apple/swift-nio-transport-services.git from cache (3.71s)
Fetched https://github.com/apple/swift-nio-http2.git from cache (3.71s)
Computing version for https://github.com/apple/swift-nio-transport-services.git
Computed https://github.com/apple/swift-nio-transport-services.git at 1.24.0 (4.16s)
Computing version for https://github.com/apple/swift-nio-http2.git
Computed https://github.com/apple/swift-nio-http2.git at 1.36.0 (0.41s)
Computing version for https://github.com/apple/swift-nio.git
Computed https://github.com/apple/swift-nio.git at 2.83.0 (0.62s)
Fetching https://github.com/apple/swift-system.git
Fetching https://github.com/apple/swift-collections.git
[1/4428] Fetching swift-system
[46/21068] Fetching swift-system, swift-collections
Fetched https://github.com/apple/swift-system.git from cache (1.03s)
[832/16640] Fetching swift-collections
Fetched https://github.com/apple/swift-collections.git from cache (1.63s)
Computing version for https://github.com/apple/swift-atomics.git
Computed https://github.com/apple/swift-atomics.git at 1.3.0 (2.06s)
Computing version for https://github.com/apple/swift-nio-ssl.git
Computed https://github.com/apple/swift-nio-ssl.git at 2.32.0 (0.53s)
Computing version for https://github.com/apple/swift-algorithms.git
Computed https://github.com/apple/swift-algorithms.git at 1.2.1 (0.48s)
Fetching https://github.com/apple/swift-numerics.git
[1/5757] Fetching swift-numerics
Fetched https://github.com/apple/swift-numerics.git from cache (1.01s)
Computing version for https://github.com/apple/swift-nio-extras.git
Computed https://github.com/apple/swift-nio-extras.git at 1.28.0 (1.47s)
Fetching https://github.com/apple/swift-async-algorithms.git
Fetching https://github.com/apple/swift-certificates.git
Fetching https://github.com/apple/swift-asn1.git
Fetching https://github.com/swift-server/swift-service-lifecycle.git
Fetching https://github.com/apple/swift-http-structured-headers.git
Fetching https://github.com/apple/swift-http-types.git
[1/1141] Fetching swift-http-structured-headers
[47/3567] Fetching swift-http-structured-headers, swift-service-lifecycle
[96/5157] Fetching swift-http-structured-headers, swift-service-lifecycle, swift-asn1
[376/10142] Fetching swift-http-structured-headers, swift-service-lifecycle, swift-asn1, swift-async-algorithms
[377/11046] Fetching swift-http-structured-headers, swift-service-lifecycle, swift-asn1, swift-async-algorithms, swift-http-types
[2360/17230] Fetching swift-http-structured-headers, swift-service-lifecycle, swift-asn1, swift-async-algorithms, swift-http-types, swift-certificates
Fetched https://github.com/apple/swift-async-algorithms.git from cache (1.02s)
[7484/12245] Fetching swift-http-structured-headers, swift-service-lifecycle, swift-asn1, swift-http-types, swift-certificates
Fetched https://github.com/apple/swift-certificates.git from cache (1.24s)
Fetched https://github.com/apple/swift-http-types.git from cache (1.24s)
Fetched https://github.com/apple/swift-asn1.git from cache (1.24s)
Fetched https://github.com/apple/swift-http-structured-headers.git from cache (1.24s)
Fetched https://github.com/swift-server/swift-service-lifecycle.git from cache (1.24s)
Computing version for https://github.com/swift-server/swift-service-lifecycle.git
Computed https://github.com/swift-server/swift-service-lifecycle.git at 2.8.0 (1.68s)
Computing version for https://github.com/apple/swift-async-algorithms.git
Computed https://github.com/apple/swift-async-algorithms.git at 1.0.4 (0.50s)
Computing version for https://github.com/apple/swift-certificates.git
Computed https://github.com/apple/swift-certificates.git at 1.10.0 (0.53s)
Fetching https://github.com/apple/swift-crypto.git
[1/15203] Fetching swift-crypto
Fetched https://github.com/apple/swift-crypto.git from cache (1.78s)
Computing version for https://github.com/apple/swift-crypto.git
Computed https://github.com/apple/swift-crypto.git at 3.12.3 (2.53s)
Computing version for https://github.com/apple/swift-asn1.git
Computed https://github.com/apple/swift-asn1.git at 1.3.2 (0.51s)
Computing version for https://github.com/apple/swift-http-types.git
Computed https://github.com/apple/swift-http-types.git at 1.4.0 (0.42s)
Computing version for https://github.com/apple/swift-system.git
Computed https://github.com/apple/swift-system.git at 1.5.0 (0.41s)
Computing version for https://github.com/apple/swift-numerics.git
Computed https://github.com/apple/swift-numerics.git at 1.0.3 (0.54s)
Computing version for https://github.com/apple/swift-http-structured-headers.git
Computed https://github.com/apple/swift-http-structured-headers.git at 1.3.0 (0.42s)
Computing version for https://github.com/apple/swift-collections.git
Computed https://github.com/apple/swift-collections.git at 1.2.0 (0.50s)
Creating working copy for https://github.com/apple/swift-collections.git
Working copy of https://github.com/apple/swift-collections.git resolved at 1.2.0
Creating working copy for https://github.com/apple/swift-nio.git
Working copy of https://github.com/apple/swift-nio.git resolved at 2.83.0
Creating working copy for https://github.com/apple/swift-system.git
Working copy of https://github.com/apple/swift-system.git resolved at 1.5.0
Creating working copy for https://github.com/apple/swift-http-types.git
Working copy of https://github.com/apple/swift-http-types.git resolved at 1.4.0
Creating working copy for https://github.com/apple/swift-atomics.git
Working copy of https://github.com/apple/swift-atomics.git resolved at 1.3.0
Creating working copy for https://github.com/apple/swift-certificates.git
Working copy of https://github.com/apple/swift-certificates.git resolved at 1.10.0
Creating working copy for https://github.com/apple/swift-log.git
Working copy of https://github.com/apple/swift-log.git resolved at 1.6.3
Creating working copy for https://github.com/apple/swift-async-algorithms.git
Working copy of https://github.com/apple/swift-async-algorithms.git resolved at 1.0.4
Creating working copy for https://github.com/apple/swift-crypto.git
Working copy of https://github.com/apple/swift-crypto.git resolved at 3.12.3
Creating working copy for https://github.com/swift-server/async-http-client.git
Working copy of https://github.com/swift-server/async-http-client.git resolved at 1.26.1
Creating working copy for https://github.com/apple/swift-numerics.git
Working copy of https://github.com/apple/swift-numerics.git resolved at 1.0.3
Creating working copy for https://github.com/apple/swift-asn1.git
Working copy of https://github.com/apple/swift-asn1.git resolved at 1.3.2
Creating working copy for https://github.com/apple/swift-nio-http2.git
Working copy of https://github.com/apple/swift-nio-http2.git resolved at 1.36.0
Creating working copy for https://github.com/apple/swift-nio-ssl.git
Working copy of https://github.com/apple/swift-nio-ssl.git resolved at 2.32.0
Creating working copy for https://github.com/swift-server/swift-service-lifecycle.git
Working copy of https://github.com/swift-server/swift-service-lifecycle.git resolved at 2.8.0
Creating working copy for https://github.com/apple/swift-nio-transport-services.git
Working copy of https://github.com/apple/swift-nio-transport-services.git resolved at 1.24.0
Creating working copy for https://github.com/apple/swift-algorithms.git
Working copy of https://github.com/apple/swift-algorithms.git resolved at 1.2.1
Creating working copy for https://github.com/apple/swift-nio-extras.git
Working copy of https://github.com/apple/swift-nio-extras.git resolved at 1.28.0
Creating working copy for https://github.com/apple/swift-http-structured-headers.git
Working copy of https://github.com/apple/swift-http-structured-headers.git resolved at 1.3.0
Build complete.
{
  "dependencies" : [
    {
      "identity" : "swift-log",
      "requirement" : {
        "range" : [
          {
            "lower_bound" : "1.2.0",
            "upper_bound" : "2.0.0"
          }
        ]
      },
      "type" : "sourceControl",
      "url" : "https://github.com/apple/swift-log.git"
    },
    {
      "identity" : "async-http-client",
      "requirement" : {
        "range" : [
          {
            "lower_bound" : "1.1.0",
            "upper_bound" : "2.0.0"
          }
        ]
      },
      "type" : "sourceControl",
      "url" : "https://github.com/swift-server/async-http-client.git"
    },
    {
      "identity" : "swift-nio",
      "requirement" : {
        "range" : [
          {
            "lower_bound" : "2.18.0",
            "upper_bound" : "3.0.0"
          }
        ]
      },
      "type" : "sourceControl",
      "url" : "https://github.com/apple/swift-nio.git"
    }
  ],
  "manifest_display_name" : "Telegrammer",
  "name" : "Telegrammer",
  "path" : "/Users/admin/builder/spi-builder-workspace",
  "platforms" : [
    {
      "name" : "macos",
      "version" : "10.14"
    }
  ],
  "products" : [
    {
      "name" : "Telegrammer",
      "targets" : [
        "Telegrammer"
      ],
      "type" : {
        "library" : [
          "automatic"
        ]
      }
    },
    {
      "name" : "TelegrammerMultipart",
      "targets" : [
        "TelegrammerMultipart"
      ],
      "type" : {
        "library" : [
          "automatic"
        ]
      }
    },
    {
      "name" : "TelegrammerCMultipartParser",
      "targets" : [
        "TelegrammerCMultipartParser"
      ],
      "type" : {
        "library" : [
          "automatic"
        ]
      }
    },
    {
      "name" : "EchoBot",
      "targets" : [
        "DemoEchoBot"
      ],
      "type" : {
        "executable" : null
      }
    },
    {
      "name" : "HelloBot",
      "targets" : [
        "DemoHelloBot"
      ],
      "type" : {
        "executable" : null
      }
    },
    {
      "name" : "SchedulerBot",
      "targets" : [
        "DemoSchedulerBot"
      ],
      "type" : {
        "executable" : null
      }
    },
    {
      "name" : "SpellCheckerBot",
      "targets" : [
        "DemoSpellCheckerBot"
      ],
      "type" : {
        "executable" : null
      }
    },
    {
      "name" : "WebhooksLocally",
      "targets" : [
        "DemoWebhooksLocally"
      ],
      "type" : {
        "executable" : null
      }
    }
  ],
  "targets" : [
    {
      "c99name" : "TelegrammerTests",
      "module_type" : "SwiftTarget",
      "name" : "TelegrammerTests",
      "path" : "Tests/TelegrammerTests",
      "sources" : [
        "FilterTests/EntityFilterTest.swift",
        "FilterTests/PrivateFilterTest.swift",
        "HandlerTests/CommandHandlerTest.swift",
        "Helpers/Test+Helpers.swift",
        "JobQueueTests/DailyJobTests.swift",
        "JobQueueTests/JobQueueTests.swift",
        "XCTestManifests.swift"
      ],
      "target_dependencies" : [
        "Telegrammer"
      ],
      "type" : "test"
    },
    {
      "c99name" : "TelegrammerMultipartTests",
      "module_type" : "SwiftTarget",
      "name" : "TelegrammerMultipartTests",
      "path" : "Tests/TelegrammerMultipartTests",
      "sources" : [
        "MultipartKitTests.swift"
      ],
      "target_dependencies" : [
        "TelegrammerCMultipartParser"
      ],
      "type" : "test"
    },
    {
      "c99name" : "TelegrammerMultipart",
      "module_type" : "SwiftTarget",
      "name" : "TelegrammerMultipart",
      "path" : "Sources/TelegrammerMultipart",
      "product_dependencies" : [
        "NIO",
        "NIOHTTP1"
      ],
      "product_memberships" : [
        "Telegrammer",
        "TelegrammerMultipart",
        "EchoBot",
        "HelloBot",
        "SchedulerBot",
        "SpellCheckerBot",
        "WebhooksLocally"
      ],
      "sources" : [
        "BasicCodingKey.swift",
        "Exports.swift",
        "FormDataDecoder.swift",
        "FormDataEncoder.swift",
        "MultipartError.swift",
        "MultipartParser.swift",
        "MultipartPart.swift",
        "MultipartPartConvertible.swift",
        "MultipartSerializer.swift",
        "Utilities.swift"
      ],
      "target_dependencies" : [
        "TelegrammerCMultipartParser"
      ],
      "type" : "library"
    },
    {
      "c99name" : "TelegrammerCMultipartParser",
      "module_type" : "ClangTarget",
      "name" : "TelegrammerCMultipartParser",
      "path" : "Sources/TelegrammerCMultipartParser",
      "product_memberships" : [
        "Telegrammer",
        "TelegrammerMultipart",
        "TelegrammerCMultipartParser",
        "EchoBot",
        "HelloBot",
        "SchedulerBot",
        "SpellCheckerBot",
        "WebhooksLocally"
      ],
      "sources" : [
        "multipartparser.c"
      ],
      "type" : "library"
    },
    {
      "c99name" : "Telegrammer",
      "module_type" : "SwiftTarget",
      "name" : "Telegrammer",
      "path" : "Sources/Telegrammer",
      "product_dependencies" : [
        "AsyncHTTPClient",
        "Logging"
      ],
      "product_memberships" : [
        "Telegrammer",
        "EchoBot",
        "HelloBot",
        "SchedulerBot",
        "SpellCheckerBot",
        "WebhooksLocally"
      ],
      "sources" : [
        "Bot/BotProtocol.swift",
        "Bot/Telegram/Bot.swift",
        "Bot/Telegram/Extensions/Message+Helpers.swift",
        "Bot/Telegram/Jobs/BasicJobQueue.swift",
        "Bot/Telegram/Jobs/DailyJob.swift",
        "Bot/Telegram/Jobs/Day.swift",
        "Bot/Telegram/Jobs/Job.swift",
        "Bot/Telegram/Jobs/JobQueue.swift",
        "Bot/Telegram/Jobs/OnceJob.swift",
        "Bot/Telegram/Jobs/RepeatableJob.swift",
        "Bot/Telegram/Methods/Bot+addStickerToSet.swift",
        "Bot/Telegram/Methods/Bot+answerCallbackQuery.swift",
        "Bot/Telegram/Methods/Bot+answerInlineQuery.swift",
        "Bot/Telegram/Methods/Bot+answerPreCheckoutQuery.swift",
        "Bot/Telegram/Methods/Bot+answerShippingQuery.swift",
        "Bot/Telegram/Methods/Bot+createNewStickerSet.swift",
        "Bot/Telegram/Methods/Bot+deleteChatPhoto.swift",
        "Bot/Telegram/Methods/Bot+deleteChatStickerSet.swift",
        "Bot/Telegram/Methods/Bot+deleteMessage.swift",
        "Bot/Telegram/Methods/Bot+deleteStickerFromSet.swift",
        "Bot/Telegram/Methods/Bot+deleteWebhook.swift",
        "Bot/Telegram/Methods/Bot+editMessageCaption.swift",
        "Bot/Telegram/Methods/Bot+editMessageLiveLocation.swift",
        "Bot/Telegram/Methods/Bot+editMessageMedia.swift",
        "Bot/Telegram/Methods/Bot+editMessageReplyMarkup.swift",
        "Bot/Telegram/Methods/Bot+editMessageText.swift",
        "Bot/Telegram/Methods/Bot+exportChatInviteLink.swift",
        "Bot/Telegram/Methods/Bot+forwardMessage.swift",
        "Bot/Telegram/Methods/Bot+getChat.swift",
        "Bot/Telegram/Methods/Bot+getChatAdministrators.swift",
        "Bot/Telegram/Methods/Bot+getChatMember.swift",
        "Bot/Telegram/Methods/Bot+getChatMembersCount.swift",
        "Bot/Telegram/Methods/Bot+getFile.swift",
        "Bot/Telegram/Methods/Bot+getGameHighScores.swift",
        "Bot/Telegram/Methods/Bot+getMe.swift",
        "Bot/Telegram/Methods/Bot+getMyCommands.swift",
        "Bot/Telegram/Methods/Bot+getStickerSet.swift",
        "Bot/Telegram/Methods/Bot+getUpdates.swift",
        "Bot/Telegram/Methods/Bot+getUserProfilePhotos.swift",
        "Bot/Telegram/Methods/Bot+getWebhookInfo.swift",
        "Bot/Telegram/Methods/Bot+kickChatMember.swift",
        "Bot/Telegram/Methods/Bot+leaveChat.swift",
        "Bot/Telegram/Methods/Bot+pinChatMessage.swift",
        "Bot/Telegram/Methods/Bot+promoteChatMember.swift",
        "Bot/Telegram/Methods/Bot+restrictChatMember.swift",
        "Bot/Telegram/Methods/Bot+sendAnimation.swift",
        "Bot/Telegram/Methods/Bot+sendAudio.swift",
        "Bot/Telegram/Methods/Bot+sendChatAction.swift",
        "Bot/Telegram/Methods/Bot+sendContact.swift",
        "Bot/Telegram/Methods/Bot+sendDice.swift",
        "Bot/Telegram/Methods/Bot+sendDocument.swift",
        "Bot/Telegram/Methods/Bot+sendGame.swift",
        "Bot/Telegram/Methods/Bot+sendInvoice.swift",
        "Bot/Telegram/Methods/Bot+sendLocation.swift",
        "Bot/Telegram/Methods/Bot+sendMediaGroup.swift",
        "Bot/Telegram/Methods/Bot+sendMessage.swift",
        "Bot/Telegram/Methods/Bot+sendPhoto.swift",
        "Bot/Telegram/Methods/Bot+sendPoll.swift",
        "Bot/Telegram/Methods/Bot+sendSticker.swift",
        "Bot/Telegram/Methods/Bot+sendVenue.swift",
        "Bot/Telegram/Methods/Bot+sendVideo.swift",
        "Bot/Telegram/Methods/Bot+sendVideoNote.swift",
        "Bot/Telegram/Methods/Bot+sendVoice.swift",
        "Bot/Telegram/Methods/Bot+setChatAdministratorCustomTitle.swift",
        "Bot/Telegram/Methods/Bot+setChatDescription.swift",
        "Bot/Telegram/Methods/Bot+setChatPermissions.swift",
        "Bot/Telegram/Methods/Bot+setChatPhoto.swift",
        "Bot/Telegram/Methods/Bot+setChatStickerSet.swift",
        "Bot/Telegram/Methods/Bot+setChatTitle.swift",
        "Bot/Telegram/Methods/Bot+setGameScore.swift",
        "Bot/Telegram/Methods/Bot+setMyCommands.swift",
        "Bot/Telegram/Methods/Bot+setPassportDataErrors.swift",
        "Bot/Telegram/Methods/Bot+setStickerPositionInSet.swift",
        "Bot/Telegram/Methods/Bot+setStickerSetThumb.swift",
        "Bot/Telegram/Methods/Bot+setWebhook.swift",
        "Bot/Telegram/Methods/Bot+stopMessageLiveLocation.swift",
        "Bot/Telegram/Methods/Bot+stopPoll.swift",
        "Bot/Telegram/Methods/Bot+unbanChatMember.swift",
        "Bot/Telegram/Methods/Bot+unpinChatMessage.swift",
        "Bot/Telegram/Methods/Bot+uploadStickerFile.swift",
        "Bot/Telegram/Models/Animation.swift",
        "Bot/Telegram/Models/Audio.swift",
        "Bot/Telegram/Models/BotCommand.swift",
        "Bot/Telegram/Models/CallbackGame.swift",
        "Bot/Telegram/Models/CallbackQuery.swift",
        "Bot/Telegram/Models/Chat.swift",
        "Bot/Telegram/Models/ChatMember.swift",
        "Bot/Telegram/Models/ChatPermissions.swift",
        "Bot/Telegram/Models/ChatPhoto.swift",
        "Bot/Telegram/Models/ChosenInlineResult.swift",
        "Bot/Telegram/Models/Contact.swift",
        "Bot/Telegram/Models/Dice.swift",
        "Bot/Telegram/Models/Document.swift",
        "Bot/Telegram/Models/EncryptedCredentials.swift",
        "Bot/Telegram/Models/EncryptedPassportElement.swift",
        "Bot/Telegram/Models/File.swift",
        "Bot/Telegram/Models/ForceReply.swift",
        "Bot/Telegram/Models/Game.swift",
        "Bot/Telegram/Models/GameHighScore.swift",
        "Bot/Telegram/Models/InlineKeyboardButton.swift",
        "Bot/Telegram/Models/InlineKeyboardMarkup.swift",
        "Bot/Telegram/Models/InlineQuery.swift",
        "Bot/Telegram/Models/InlineQueryResultArticle.swift",
        "Bot/Telegram/Models/InlineQueryResultAudio.swift",
        "Bot/Telegram/Models/InlineQueryResultCachedAudio.swift",
        "Bot/Telegram/Models/InlineQueryResultCachedDocument.swift",
        "Bot/Telegram/Models/InlineQueryResultCachedGif.swift",
        "Bot/Telegram/Models/InlineQueryResultCachedMpeg4Gif.swift",
        "Bot/Telegram/Models/InlineQueryResultCachedPhoto.swift",
        "Bot/Telegram/Models/InlineQueryResultCachedSticker.swift",
        "Bot/Telegram/Models/InlineQueryResultCachedVideo.swift",
        "Bot/Telegram/Models/InlineQueryResultCachedVoice.swift",
        "Bot/Telegram/Models/InlineQueryResultContact.swift",
        "Bot/Telegram/Models/InlineQueryResultDocument.swift",
        "Bot/Telegram/Models/InlineQueryResultGame.swift",
        "Bot/Telegram/Models/InlineQueryResultGif.swift",
        "Bot/Telegram/Models/InlineQueryResultLocation.swift",
        "Bot/Telegram/Models/InlineQueryResultMpeg4Gif.swift",
        "Bot/Telegram/Models/InlineQueryResultPhoto.swift",
        "Bot/Telegram/Models/InlineQueryResultVenue.swift",
        "Bot/Telegram/Models/InlineQueryResultVideo.swift",
        "Bot/Telegram/Models/InlineQueryResultVoice.swift",
        "Bot/Telegram/Models/InputContactMessageContent.swift",
        "Bot/Telegram/Models/InputLocationMessageContent.swift",
        "Bot/Telegram/Models/InputMediaAnimation.swift",
        "Bot/Telegram/Models/InputMediaAudio.swift",
        "Bot/Telegram/Models/InputMediaDocument.swift",
        "Bot/Telegram/Models/InputMediaPhoto.swift",
        "Bot/Telegram/Models/InputMediaVideo.swift",
        "Bot/Telegram/Models/InputTextMessageContent.swift",
        "Bot/Telegram/Models/InputVenueMessageContent.swift",
        "Bot/Telegram/Models/Invoice.swift",
        "Bot/Telegram/Models/KeyboardButton.swift",
        "Bot/Telegram/Models/KeyboardButtonPollType.swift",
        "Bot/Telegram/Models/LabeledPrice.swift",
        "Bot/Telegram/Models/Location.swift",
        "Bot/Telegram/Models/LoginUrl.swift",
        "Bot/Telegram/Models/MaskPosition.swift",
        "Bot/Telegram/Models/Message.swift",
        "Bot/Telegram/Models/MessageEntity.swift",
        "Bot/Telegram/Models/OrderInfo.swift",
        "Bot/Telegram/Models/PassportData.swift",
        "Bot/Telegram/Models/PassportElementErrorDataField.swift",
        "Bot/Telegram/Models/PassportElementErrorFile.swift",
        "Bot/Telegram/Models/PassportElementErrorFiles.swift",
        "Bot/Telegram/Models/PassportElementErrorFrontSide.swift",
        "Bot/Telegram/Models/PassportElementErrorReverseSide.swift",
        "Bot/Telegram/Models/PassportElementErrorSelfie.swift",
        "Bot/Telegram/Models/PassportElementErrorTranslationFile.swift",
        "Bot/Telegram/Models/PassportElementErrorTranslationFiles.swift",
        "Bot/Telegram/Models/PassportElementErrorUnspecified.swift",
        "Bot/Telegram/Models/PassportFile.swift",
        "Bot/Telegram/Models/PhotoSize.swift",
        "Bot/Telegram/Models/Poll.swift",
        "Bot/Telegram/Models/PollAnswer.swift",
        "Bot/Telegram/Models/PollOption.swift",
        "Bot/Telegram/Models/PreCheckoutQuery.swift",
        "Bot/Telegram/Models/ReplyKeyboardMarkup.swift",
        "Bot/Telegram/Models/ReplyKeyboardRemove.swift",
        "Bot/Telegram/Models/ResponseParameters.swift",
        "Bot/Telegram/Models/ShippingAddress.swift",
        "Bot/Telegram/Models/ShippingOption.swift",
        "Bot/Telegram/Models/ShippingQuery.swift",
        "Bot/Telegram/Models/Sticker.swift",
        "Bot/Telegram/Models/StickerSet.swift",
        "Bot/Telegram/Models/SuccessfulPayment.swift",
        "Bot/Telegram/Models/Update.swift",
        "Bot/Telegram/Models/User.swift",
        "Bot/Telegram/Models/UserProfilePhotos.swift",
        "Bot/Telegram/Models/Venue.swift",
        "Bot/Telegram/Models/Video.swift",
        "Bot/Telegram/Models/VideoNote.swift",
        "Bot/Telegram/Models/Voice.swift",
        "Bot/Telegram/Models/WebhookInfo.swift",
        "Bot/Telegram/Storage/Storage.swift",
        "Dispatcher/Dispatcher.swift",
        "Dispatcher/HandlerGroup.swift",
        "Dispatcher/HandlersQueue.swift",
        "Errors/BotError.swift",
        "Filters/AllFilter.swift",
        "Filters/AudioFilter.swift",
        "Filters/CaptionEntityFilter.swift",
        "Filters/ChatFilter.swift",
        "Filters/CommandFilter.swift",
        "Filters/ContactFilter.swift",
        "Filters/DocumentFilter.swift",
        "Filters/EntityFilter.swift",
        "Filters/Filter.swift",
        "Filters/ForwarderFilter.swift",
        "Filters/GameFilter.swift",
        "Filters/GroupFilter.swift",
        "Filters/InvoiceFilter.swift",
        "Filters/LanguageFilter.swift",
        "Filters/LocationFilter.swift",
        "Filters/PhotoFilter.swift",
        "Filters/PrivateFilter.swift",
        "Filters/RegexpFilter.swift",
        "Filters/ReplyFilter.swift",
        "Filters/StatusUpdateFilters.swift",
        "Filters/StickerFilter.swift",
        "Filters/SuccesfulPaymentFilter.swift",
        "Filters/TextFilter.swift",
        "Filters/UserFilter.swift",
        "Filters/VenueFilter.swift",
        "Filters/VideoFilter.swift",
        "Filters/VideoNoteFilter.swift",
        "Filters/VoiceFilter.swift",
        "Handlers/CallbackQueryHandler.swift",
        "Handlers/CommandHandler.swift",
        "Handlers/ConversationHandler.swift",
        "Handlers/Handler.swift",
        "Handlers/LoggerHandler.swift",
        "Handlers/MessageHandler.swift",
        "Handlers/RegexpHandler.swift",
        "Helpers/Constants.swift",
        "Helpers/Enviroment+Helper.swift",
        "Helpers/Error+Helpers.swift",
        "Helpers/HTTPHeader+Helper.swift",
        "Helpers/HTTPRequest+Helper.swift",
        "Helpers/MultipartPartConvertible+Helper.swift",
        "Helpers/String+Helper.swift",
        "Helpers/SynchronizedArray.swift",
        "Helpers/TimeAmount+Helpers.swift",
        "Network/Bot.Settings+Proxy.swift",
        "Network/BotClient.swift",
        "Network/Longpolling.swift",
        "Network/Network.swift",
        "Network/UpdatesServer.swift",
        "Network/Webhooks.swift",
        "Types/ChatId.swift",
        "Types/ChatType.swift",
        "Types/FileInfo.swift",
        "Types/InlineQueryResult.swift",
        "Types/InputFile.swift",
        "Types/InputMedia.swift",
        "Types/InputMessageContent.swift",
        "Types/MessageEntityType.swift",
        "Types/MessageOrBool.swift",
        "Types/ParseMode.swift",
        "Types/PassportElementError.swift",
        "Types/ReplyMarkup.swift",
        "Types/TelegramContainer.swift",
        "Types/TelegramEncodables.swift",
        "Updater/Updater.swift"
      ],
      "target_dependencies" : [
        "TelegrammerMultipart"
      ],
      "type" : "library"
    },
    {
      "c99name" : "DemoWebhooksLocally",
      "module_type" : "SwiftTarget",
      "name" : "DemoWebhooksLocally",
      "path" : "Sources/DemoWebhooksLocally",
      "product_memberships" : [
        "WebhooksLocally"
      ],
      "sources" : [
        "main.swift"
      ],
      "target_dependencies" : [
        "Telegrammer"
      ],
      "type" : "executable"
    },
    {
      "c99name" : "DemoSpellCheckerBot",
      "module_type" : "SwiftTarget",
      "name" : "DemoSpellCheckerBot",
      "path" : "Sources/DemoSpellCheckerBot",
      "product_memberships" : [
        "SpellCheckerBot"
      ],
      "sources" : [
        "Controllers/SpellCheckerController.swift",
        "Helpers/Array+Helper.swift",
        "SpellChecker/SpellChecker.swift",
        "SpellChecker/YaSpellCheck.swift",
        "SpellChecker/YaSpellChecker.swift",
        "SpellChecker/YaSpellFlow.swift",
        "main.swift"
      ],
      "target_dependencies" : [
        "Telegrammer"
      ],
      "type" : "executable"
    },
    {
      "c99name" : "DemoSchedulerBot",
      "module_type" : "SwiftTarget",
      "name" : "DemoSchedulerBot",
      "path" : "Sources/DemoSchedulerBot",
      "product_memberships" : [
        "SchedulerBot"
      ],
      "sources" : [
        "main.swift"
      ],
      "target_dependencies" : [
        "Telegrammer"
      ],
      "type" : "executable"
    },
    {
      "c99name" : "DemoHelloBot",
      "module_type" : "SwiftTarget",
      "name" : "DemoHelloBot",
      "path" : "Sources/DemoHelloBot",
      "product_memberships" : [
        "HelloBot"
      ],
      "sources" : [
        "Handlers/NewMemberHandler.swift",
        "main.swift"
      ],
      "target_dependencies" : [
        "Telegrammer"
      ],
      "type" : "executable"
    },
    {
      "c99name" : "DemoEchoBot",
      "module_type" : "SwiftTarget",
      "name" : "DemoEchoBot",
      "path" : "Sources/DemoEchoBot",
      "product_memberships" : [
        "EchoBot"
      ],
      "sources" : [
        "main.swift"
      ],
      "target_dependencies" : [
        "Telegrammer"
      ],
      "type" : "executable"
    }
  ],
  "tools_version" : "5.2"
}
Done.