Swift Package IndexBuild Information
Successful build of Telegrammer, reference master (459176), with Swift 6.1 for macOS (SPM) on 25 Apr 2025 17:42:27 UTC.
Swift 6 data race errors: 37
Build Command
env DEVELOPER_DIR=/Applications/Xcode-16.3.0.app xcrun swift build --arch arm64Build Log
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendContact.swift:74:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
72 | */
73 | @discardableResult
74 | func sendContact(params: SendContactParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
75 | let body = try httpBody(for: params)
76 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendDice.swift:59:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
57 | */
58 | @discardableResult
59 | func sendDice(params: SendDiceParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
60 | let body = try httpBody(for: params)
61 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendDocument.swift:84:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
82 | */
83 | @discardableResult
84 | func sendDocument(params: SendDocumentParams) 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:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendGame.swift:59:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
57 | */
58 | @discardableResult
59 | func sendGame(params: SendGameParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
60 | let body = try httpBody(for: params)
61 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendInvoice.swift:159:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
157 | */
158 | @discardableResult
159 | func sendInvoice(params: SendInvoiceParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
160 | let body = try httpBody(for: params)
161 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendLocation.swift:84:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
82 | */
83 | @discardableResult
84 | func sendLocation(params: SendLocationParams) 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:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendMediaGroup.swift:54:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
52 | */
53 | @discardableResult
54 | func sendMediaGroup(params: SendMediaGroupParams) 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:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendMessage.swift:74:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
72 | */
73 | @discardableResult
74 | func sendMessage(params: SendMessageParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
75 | let body = try httpBody(for: params)
76 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendPhoto.swift:74:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
72 | */
73 | @discardableResult
74 | func sendPhoto(params: SendPhotoParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
75 | let body = try httpBody(for: params)
76 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendPoll.swift:114:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
112 | */
113 | @discardableResult
114 | func sendPoll(params: SendPollParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
115 | let body = try httpBody(for: params)
116 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendSticker.swift:59:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
57 | */
58 | @discardableResult
59 | func sendSticker(params: SendStickerParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
60 | let body = try httpBody(for: params)
61 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendVenue.swift:94:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
92 | */
93 | @discardableResult
94 | func sendVenue(params: SendVenueParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
95 | let body = try httpBody(for: params)
96 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendVideo.swift:99:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
97 | */
98 | @discardableResult
99 | func sendVideo(params: SendVideoParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
100 | let body = try httpBody(for: params)
101 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendVideoNote.swift:74:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
72 | */
73 | @discardableResult
74 | func sendVideoNote(params: SendVideoNoteParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
75 | let body = try httpBody(for: params)
76 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendVoice.swift:79:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
77 | */
78 | @discardableResult
79 | func sendVoice(params: SendVoiceParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
80 | let body = try httpBody(for: params)
81 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
[422/486] Compiling Telegrammer Bot+sendVenue.swift
/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:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+logOut.swift:18:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
16 | */
17 | @discardableResult
18 | func logOut() throws -> Future<Bool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
19 | return try client
20 | .request(endpoint: "logOut")
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+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:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+promoteChatMember.swift:94:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
92 | */
93 | @discardableResult
94 | func promoteChatMember(params: PromoteChatMemberParams) throws -> Future<Bool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
95 | let body = try httpBody(for: params)
96 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+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:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+revokeChatInviteLink.swift:39:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
37 | */
38 | @discardableResult
39 | func revokeChatInviteLink(params: RevokeChatInviteLinkParams) throws -> Future<Bool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
40 | let body = try httpBody(for: params)
41 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendAnimation.swift:94:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
92 | */
93 | @discardableResult
94 | func sendAnimation(params: SendAnimationParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
95 | let body = try httpBody(for: params)
96 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendAudio.swift:95:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
93 | */
94 | @discardableResult
95 | func sendAudio(params: SendAudioParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
96 | let body = try httpBody(for: params)
97 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+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:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendContact.swift:74:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
72 | */
73 | @discardableResult
74 | func sendContact(params: SendContactParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
75 | let body = try httpBody(for: params)
76 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendDice.swift:59:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
57 | */
58 | @discardableResult
59 | func sendDice(params: SendDiceParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
60 | let body = try httpBody(for: params)
61 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendDocument.swift:84:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
82 | */
83 | @discardableResult
84 | func sendDocument(params: SendDocumentParams) 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:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendGame.swift:59:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
57 | */
58 | @discardableResult
59 | func sendGame(params: SendGameParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
60 | let body = try httpBody(for: params)
61 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendInvoice.swift:159:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
157 | */
158 | @discardableResult
159 | func sendInvoice(params: SendInvoiceParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
160 | let body = try httpBody(for: params)
161 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendLocation.swift:84:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
82 | */
83 | @discardableResult
84 | func sendLocation(params: SendLocationParams) 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:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendMediaGroup.swift:54:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
52 | */
53 | @discardableResult
54 | func sendMediaGroup(params: SendMediaGroupParams) 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:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendMessage.swift:74:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
72 | */
73 | @discardableResult
74 | func sendMessage(params: SendMessageParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
75 | let body = try httpBody(for: params)
76 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendPhoto.swift:74:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
72 | */
73 | @discardableResult
74 | func sendPhoto(params: SendPhotoParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
75 | let body = try httpBody(for: params)
76 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendPoll.swift:114:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
112 | */
113 | @discardableResult
114 | func sendPoll(params: SendPollParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
115 | let body = try httpBody(for: params)
116 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendSticker.swift:59:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
57 | */
58 | @discardableResult
59 | func sendSticker(params: SendStickerParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
60 | let body = try httpBody(for: params)
61 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendVenue.swift:94:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
92 | */
93 | @discardableResult
94 | func sendVenue(params: SendVenueParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
95 | let body = try httpBody(for: params)
96 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendVideo.swift:99:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
97 | */
98 | @discardableResult
99 | func sendVideo(params: SendVideoParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
100 | let body = try httpBody(for: params)
101 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendVideoNote.swift:74:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
72 | */
73 | @discardableResult
74 | func sendVideoNote(params: SendVideoNoteParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
75 | let body = try httpBody(for: params)
76 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendVoice.swift:79:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
77 | */
78 | @discardableResult
79 | func sendVoice(params: SendVoiceParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
80 | let body = try httpBody(for: params)
81 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
[423/486] Compiling Telegrammer Bot+sendVideo.swift
/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:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+logOut.swift:18:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
16 | */
17 | @discardableResult
18 | func logOut() throws -> Future<Bool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
19 | return try client
20 | .request(endpoint: "logOut")
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+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:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+promoteChatMember.swift:94:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
92 | */
93 | @discardableResult
94 | func promoteChatMember(params: PromoteChatMemberParams) throws -> Future<Bool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
95 | let body = try httpBody(for: params)
96 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+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:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+revokeChatInviteLink.swift:39:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
37 | */
38 | @discardableResult
39 | func revokeChatInviteLink(params: RevokeChatInviteLinkParams) throws -> Future<Bool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
40 | let body = try httpBody(for: params)
41 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendAnimation.swift:94:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
92 | */
93 | @discardableResult
94 | func sendAnimation(params: SendAnimationParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
95 | let body = try httpBody(for: params)
96 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendAudio.swift:95:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
93 | */
94 | @discardableResult
95 | func sendAudio(params: SendAudioParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
96 | let body = try httpBody(for: params)
97 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+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:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendContact.swift:74:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
72 | */
73 | @discardableResult
74 | func sendContact(params: SendContactParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
75 | let body = try httpBody(for: params)
76 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendDice.swift:59:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
57 | */
58 | @discardableResult
59 | func sendDice(params: SendDiceParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
60 | let body = try httpBody(for: params)
61 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendDocument.swift:84:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
82 | */
83 | @discardableResult
84 | func sendDocument(params: SendDocumentParams) 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:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendGame.swift:59:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
57 | */
58 | @discardableResult
59 | func sendGame(params: SendGameParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
60 | let body = try httpBody(for: params)
61 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendInvoice.swift:159:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
157 | */
158 | @discardableResult
159 | func sendInvoice(params: SendInvoiceParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
160 | let body = try httpBody(for: params)
161 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendLocation.swift:84:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
82 | */
83 | @discardableResult
84 | func sendLocation(params: SendLocationParams) 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:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendMediaGroup.swift:54:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
52 | */
53 | @discardableResult
54 | func sendMediaGroup(params: SendMediaGroupParams) 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:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendMessage.swift:74:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
72 | */
73 | @discardableResult
74 | func sendMessage(params: SendMessageParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
75 | let body = try httpBody(for: params)
76 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendPhoto.swift:74:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
72 | */
73 | @discardableResult
74 | func sendPhoto(params: SendPhotoParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
75 | let body = try httpBody(for: params)
76 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendPoll.swift:114:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
112 | */
113 | @discardableResult
114 | func sendPoll(params: SendPollParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
115 | let body = try httpBody(for: params)
116 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendSticker.swift:59:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
57 | */
58 | @discardableResult
59 | func sendSticker(params: SendStickerParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
60 | let body = try httpBody(for: params)
61 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendVenue.swift:94:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
92 | */
93 | @discardableResult
94 | func sendVenue(params: SendVenueParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
95 | let body = try httpBody(for: params)
96 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendVideo.swift:99:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
97 | */
98 | @discardableResult
99 | func sendVideo(params: SendVideoParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
100 | let body = try httpBody(for: params)
101 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendVideoNote.swift:74:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
72 | */
73 | @discardableResult
74 | func sendVideoNote(params: SendVideoNoteParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
75 | let body = try httpBody(for: params)
76 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendVoice.swift:79:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
77 | */
78 | @discardableResult
79 | func sendVoice(params: SendVoiceParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
80 | let body = try httpBody(for: params)
81 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
[424/486] Compiling Telegrammer Bot+sendVideoNote.swift
/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:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+logOut.swift:18:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
16 | */
17 | @discardableResult
18 | func logOut() throws -> Future<Bool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
19 | return try client
20 | .request(endpoint: "logOut")
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+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:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+promoteChatMember.swift:94:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
92 | */
93 | @discardableResult
94 | func promoteChatMember(params: PromoteChatMemberParams) throws -> Future<Bool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
95 | let body = try httpBody(for: params)
96 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+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:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+revokeChatInviteLink.swift:39:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
37 | */
38 | @discardableResult
39 | func revokeChatInviteLink(params: RevokeChatInviteLinkParams) throws -> Future<Bool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
40 | let body = try httpBody(for: params)
41 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendAnimation.swift:94:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
92 | */
93 | @discardableResult
94 | func sendAnimation(params: SendAnimationParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
95 | let body = try httpBody(for: params)
96 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendAudio.swift:95:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
93 | */
94 | @discardableResult
95 | func sendAudio(params: SendAudioParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
96 | let body = try httpBody(for: params)
97 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+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:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendContact.swift:74:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
72 | */
73 | @discardableResult
74 | func sendContact(params: SendContactParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
75 | let body = try httpBody(for: params)
76 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendDice.swift:59:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
57 | */
58 | @discardableResult
59 | func sendDice(params: SendDiceParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
60 | let body = try httpBody(for: params)
61 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendDocument.swift:84:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
82 | */
83 | @discardableResult
84 | func sendDocument(params: SendDocumentParams) 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:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendGame.swift:59:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
57 | */
58 | @discardableResult
59 | func sendGame(params: SendGameParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
60 | let body = try httpBody(for: params)
61 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendInvoice.swift:159:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
157 | */
158 | @discardableResult
159 | func sendInvoice(params: SendInvoiceParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
160 | let body = try httpBody(for: params)
161 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendLocation.swift:84:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
82 | */
83 | @discardableResult
84 | func sendLocation(params: SendLocationParams) 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:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendMediaGroup.swift:54:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
52 | */
53 | @discardableResult
54 | func sendMediaGroup(params: SendMediaGroupParams) 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:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendMessage.swift:74:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
72 | */
73 | @discardableResult
74 | func sendMessage(params: SendMessageParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
75 | let body = try httpBody(for: params)
76 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendPhoto.swift:74:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
72 | */
73 | @discardableResult
74 | func sendPhoto(params: SendPhotoParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
75 | let body = try httpBody(for: params)
76 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendPoll.swift:114:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
112 | */
113 | @discardableResult
114 | func sendPoll(params: SendPollParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
115 | let body = try httpBody(for: params)
116 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendSticker.swift:59:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
57 | */
58 | @discardableResult
59 | func sendSticker(params: SendStickerParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
60 | let body = try httpBody(for: params)
61 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendVenue.swift:94:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
92 | */
93 | @discardableResult
94 | func sendVenue(params: SendVenueParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
95 | let body = try httpBody(for: params)
96 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendVideo.swift:99:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
97 | */
98 | @discardableResult
99 | func sendVideo(params: SendVideoParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
100 | let body = try httpBody(for: params)
101 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendVideoNote.swift:74:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
72 | */
73 | @discardableResult
74 | func sendVideoNote(params: SendVideoNoteParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
75 | let body = try httpBody(for: params)
76 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendVoice.swift:79:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
77 | */
78 | @discardableResult
79 | func sendVoice(params: SendVoiceParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
80 | let body = try httpBody(for: params)
81 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
[425/486] Compiling Telegrammer Bot+sendVoice.swift
/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:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+logOut.swift:18:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
16 | */
17 | @discardableResult
18 | func logOut() throws -> Future<Bool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
19 | return try client
20 | .request(endpoint: "logOut")
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+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:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+promoteChatMember.swift:94:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
92 | */
93 | @discardableResult
94 | func promoteChatMember(params: PromoteChatMemberParams) throws -> Future<Bool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
95 | let body = try httpBody(for: params)
96 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+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:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+revokeChatInviteLink.swift:39:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
37 | */
38 | @discardableResult
39 | func revokeChatInviteLink(params: RevokeChatInviteLinkParams) throws -> Future<Bool> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
40 | let body = try httpBody(for: params)
41 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendAnimation.swift:94:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
92 | */
93 | @discardableResult
94 | func sendAnimation(params: SendAnimationParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
95 | let body = try httpBody(for: params)
96 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendAudio.swift:95:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
93 | */
94 | @discardableResult
95 | func sendAudio(params: SendAudioParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
96 | let body = try httpBody(for: params)
97 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+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:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendContact.swift:74:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
72 | */
73 | @discardableResult
74 | func sendContact(params: SendContactParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
75 | let body = try httpBody(for: params)
76 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendDice.swift:59:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
57 | */
58 | @discardableResult
59 | func sendDice(params: SendDiceParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
60 | let body = try httpBody(for: params)
61 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendDocument.swift:84:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
82 | */
83 | @discardableResult
84 | func sendDocument(params: SendDocumentParams) 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:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendGame.swift:59:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
57 | */
58 | @discardableResult
59 | func sendGame(params: SendGameParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
60 | let body = try httpBody(for: params)
61 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendInvoice.swift:159:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
157 | */
158 | @discardableResult
159 | func sendInvoice(params: SendInvoiceParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
160 | let body = try httpBody(for: params)
161 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendLocation.swift:84:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
82 | */
83 | @discardableResult
84 | func sendLocation(params: SendLocationParams) 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:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendMediaGroup.swift:54:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
52 | */
53 | @discardableResult
54 | func sendMediaGroup(params: SendMediaGroupParams) 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:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendMessage.swift:74:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
72 | */
73 | @discardableResult
74 | func sendMessage(params: SendMessageParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
75 | let body = try httpBody(for: params)
76 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendPhoto.swift:74:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
72 | */
73 | @discardableResult
74 | func sendPhoto(params: SendPhotoParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
75 | let body = try httpBody(for: params)
76 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendPoll.swift:114:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
112 | */
113 | @discardableResult
114 | func sendPoll(params: SendPollParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
115 | let body = try httpBody(for: params)
116 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendSticker.swift:59:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
57 | */
58 | @discardableResult
59 | func sendSticker(params: SendStickerParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
60 | let body = try httpBody(for: params)
61 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendVenue.swift:94:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
92 | */
93 | @discardableResult
94 | func sendVenue(params: SendVenueParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
95 | let body = try httpBody(for: params)
96 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendVideo.swift:99:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
97 | */
98 | @discardableResult
99 | func sendVideo(params: SendVideoParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
100 | let body = try httpBody(for: params)
101 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendVideoNote.swift:74:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
72 | */
73 | @discardableResult
74 | func sendVideoNote(params: SendVideoNoteParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
75 | let body = try httpBody(for: params)
76 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Bot/Telegram/Methods/Bot+sendVoice.swift:79:10: warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
77 | */
78 | @discardableResult
79 | func sendVoice(params: SendVoiceParams) throws -> Future<Message> {
| `- warning: cannot use generic class 'EventLoopFuture' here; 'NIOCore' was not imported by this file
80 | let body = try httpBody(for: params)
81 | let headers = httpHeaders(for: params)
/Users/admin/builder/spi-builder-workspace/.build/checkouts/swift-nio/Sources/NIOCore/EventLoopFuture.swift:373:20: note: generic class declared here
371 | /// should be considered a code smell worth investigating: the `EventLoop`-based synchronization guarantees of
372 | /// `EventLoopFuture` should be sufficient to guarantee thread-safety.
373 | public final class EventLoopFuture<Value> {
| `- note: generic class declared here
374 | // TODO: Provide a tracing facility. It would be nice to be able to set '.debugTrace = true' on any EventLoopFuture or EventLoopPromise and have every subsequent chained EventLoopFuture report the success result or failure error. That would simplify some debugging scenarios.
375 | @usableFromInline
[426/509] Compiling Telegrammer Dispatcher.swift
[427/509] Compiling Telegrammer HandlerGroup.swift
[428/509] Compiling Telegrammer HandlersQueue.swift
[429/509] Compiling Telegrammer BotError.swift
[430/509] Compiling Telegrammer AllFilter.swift
[431/509] Compiling Telegrammer AudioFilter.swift
[432/509] Compiling Telegrammer CaptionEntityFilter.swift
[433/509] Compiling Telegrammer ChatFilter.swift
[434/509] Compiling Telegrammer CommandFilter.swift
[435/509] Compiling Telegrammer ContactFilter.swift
[436/509] Compiling Telegrammer DocumentFilter.swift
[437/509] Compiling Telegrammer EntityFilter.swift
[438/509] Compiling Telegrammer Filter.swift
[439/509] Compiling Telegrammer ForwarderFilter.swift
[440/509] Compiling Telegrammer GameFilter.swift
[441/509] Compiling Telegrammer GroupFilter.swift
[442/509] Compiling Telegrammer InvoiceFilter.swift
[443/509] Compiling Telegrammer LanguageFilter.swift
[444/509] Compiling Telegrammer LocationFilter.swift
[445/509] Compiling Telegrammer PhotoFilter.swift
[446/509] Compiling Telegrammer PrivateFilter.swift
[447/509] Compiling Telegrammer RegexpFilter.swift
[448/509] Compiling Telegrammer ReplyFilter.swift
[449/509] Compiling Telegrammer StatusUpdateFilters.swift
[450/509] Compiling Telegrammer StickerFilter.swift
[451/509] Compiling Telegrammer SuccesfulPaymentFilter.swift
[452/509] Compiling Telegrammer TextFilter.swift
[453/509] Compiling Telegrammer UserFilter.swift
[454/509] Compiling Telegrammer VenueFilter.swift
[455/509] Compiling Telegrammer VideoFilter.swift
[456/509] Compiling Telegrammer VideoNoteFilter.swift
[457/509] Compiling Telegrammer VoiceFilter.swift
[458/509] Compiling Telegrammer CallbackQueryHandler.swift
[459/509] Compiling Telegrammer CommandHandler.swift
[460/509] Compiling Telegrammer ConversationHandler.swift
[461/509] Compiling Telegrammer Handler.swift
[462/509] Compiling Telegrammer LoggerHandler.swift
[463/509] Compiling Telegrammer MessageHandler.swift
[464/509] Compiling Telegrammer RegexpHandler.swift
[465/509] Compiling Telegrammer Constants.swift
[466/509] Compiling Telegrammer Enviroment+Helper.swift
[467/509] Compiling Telegrammer Error+Helpers.swift
[468/509] Compiling Telegrammer HTTPHeader+Helper.swift
[469/509] Compiling Telegrammer HTTPRequest+Helper.swift
[470/509] Compiling Telegrammer MultipartPartConvertible+Helper.swift
[471/509] Compiling Telegrammer String+Helper.swift
[472/509] Compiling Telegrammer SynchronizedArray.swift
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Network/BotClient.swift:131:34: warning: converting a value of type '(__shared sending Result<TelegramContainer<T>, any Error>) -> ()' to type '(Result<TelegramContainer<T>, any Error>) -> Void' risks causing data races; this is an error in the Swift 6 language mode
129 | return try self.decode(response: response)
130 | })
131 | .whenComplete($0.resume(with: ))
| |- warning: converting a value of type '(__shared sending Result<TelegramContainer<T>, any Error>) -> ()' to type '(Result<TelegramContainer<T>, any Error>) -> Void' risks causing data races; this is an error in the Swift 6 language mode
| `- note: converting a function typed value with a sending parameter to one without risks allowing actor-isolated values to escape their isolation domain as an argument to an invocation of value
132 | }
133 | }
[473/509] Compiling Telegrammer TimeAmount+Helpers.swift
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Network/BotClient.swift:131:34: warning: converting a value of type '(__shared sending Result<TelegramContainer<T>, any Error>) -> ()' to type '(Result<TelegramContainer<T>, any Error>) -> Void' risks causing data races; this is an error in the Swift 6 language mode
129 | return try self.decode(response: response)
130 | })
131 | .whenComplete($0.resume(with: ))
| |- warning: converting a value of type '(__shared sending Result<TelegramContainer<T>, any Error>) -> ()' to type '(Result<TelegramContainer<T>, any Error>) -> Void' risks causing data races; this is an error in the Swift 6 language mode
| `- note: converting a function typed value with a sending parameter to one without risks allowing actor-isolated values to escape their isolation domain as an argument to an invocation of value
132 | }
133 | }
[474/509] Compiling Telegrammer Bot.Settings+Proxy.swift
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Network/BotClient.swift:131:34: warning: converting a value of type '(__shared sending Result<TelegramContainer<T>, any Error>) -> ()' to type '(Result<TelegramContainer<T>, any Error>) -> Void' risks causing data races; this is an error in the Swift 6 language mode
129 | return try self.decode(response: response)
130 | })
131 | .whenComplete($0.resume(with: ))
| |- warning: converting a value of type '(__shared sending Result<TelegramContainer<T>, any Error>) -> ()' to type '(Result<TelegramContainer<T>, any Error>) -> Void' risks causing data races; this is an error in the Swift 6 language mode
| `- note: converting a function typed value with a sending parameter to one without risks allowing actor-isolated values to escape their isolation domain as an argument to an invocation of value
132 | }
133 | }
[475/509] Compiling Telegrammer BotClient.swift
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Network/BotClient.swift:131:34: warning: converting a value of type '(__shared sending Result<TelegramContainer<T>, any Error>) -> ()' to type '(Result<TelegramContainer<T>, any Error>) -> Void' risks causing data races; this is an error in the Swift 6 language mode
129 | return try self.decode(response: response)
130 | })
131 | .whenComplete($0.resume(with: ))
| |- warning: converting a value of type '(__shared sending Result<TelegramContainer<T>, any Error>) -> ()' to type '(Result<TelegramContainer<T>, any Error>) -> Void' risks causing data races; this is an error in the Swift 6 language mode
| `- note: converting a function typed value with a sending parameter to one without risks allowing actor-isolated values to escape their isolation domain as an argument to an invocation of value
132 | }
133 | }
[476/509] Compiling Telegrammer Longpolling.swift
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Network/BotClient.swift:131:34: warning: converting a value of type '(__shared sending Result<TelegramContainer<T>, any Error>) -> ()' to type '(Result<TelegramContainer<T>, any Error>) -> Void' risks causing data races; this is an error in the Swift 6 language mode
129 | return try self.decode(response: response)
130 | })
131 | .whenComplete($0.resume(with: ))
| |- warning: converting a value of type '(__shared sending Result<TelegramContainer<T>, any Error>) -> ()' to type '(Result<TelegramContainer<T>, any Error>) -> Void' risks causing data races; this is an error in the Swift 6 language mode
| `- note: converting a function typed value with a sending parameter to one without risks allowing actor-isolated values to escape their isolation domain as an argument to an invocation of value
132 | }
133 | }
[477/509] Compiling Telegrammer Network.swift
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Network/BotClient.swift:131:34: warning: converting a value of type '(__shared sending Result<TelegramContainer<T>, any Error>) -> ()' to type '(Result<TelegramContainer<T>, any Error>) -> Void' risks causing data races; this is an error in the Swift 6 language mode
129 | return try self.decode(response: response)
130 | })
131 | .whenComplete($0.resume(with: ))
| |- warning: converting a value of type '(__shared sending Result<TelegramContainer<T>, any Error>) -> ()' to type '(Result<TelegramContainer<T>, any Error>) -> Void' risks causing data races; this is an error in the Swift 6 language mode
| `- note: converting a function typed value with a sending parameter to one without risks allowing actor-isolated values to escape their isolation domain as an argument to an invocation of value
132 | }
133 | }
[478/509] Compiling Telegrammer UpdatesServer.swift
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Network/BotClient.swift:131:34: warning: converting a value of type '(__shared sending Result<TelegramContainer<T>, any Error>) -> ()' to type '(Result<TelegramContainer<T>, any Error>) -> Void' risks causing data races; this is an error in the Swift 6 language mode
129 | return try self.decode(response: response)
130 | })
131 | .whenComplete($0.resume(with: ))
| |- warning: converting a value of type '(__shared sending Result<TelegramContainer<T>, any Error>) -> ()' to type '(Result<TelegramContainer<T>, any Error>) -> Void' risks causing data races; this is an error in the Swift 6 language mode
| `- note: converting a function typed value with a sending parameter to one without risks allowing actor-isolated values to escape their isolation domain as an argument to an invocation of value
132 | }
133 | }
[479/509] Compiling Telegrammer Webhooks.swift
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Network/BotClient.swift:131:34: warning: converting a value of type '(__shared sending Result<TelegramContainer<T>, any Error>) -> ()' to type '(Result<TelegramContainer<T>, any Error>) -> Void' risks causing data races; this is an error in the Swift 6 language mode
129 | return try self.decode(response: response)
130 | })
131 | .whenComplete($0.resume(with: ))
| |- warning: converting a value of type '(__shared sending Result<TelegramContainer<T>, any Error>) -> ()' to type '(Result<TelegramContainer<T>, any Error>) -> Void' risks causing data races; this is an error in the Swift 6 language mode
| `- note: converting a function typed value with a sending parameter to one without risks allowing actor-isolated values to escape their isolation domain as an argument to an invocation of value
132 | }
133 | }
[480/509] Compiling Telegrammer ChatId.swift
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Network/BotClient.swift:131:34: warning: converting a value of type '(__shared sending Result<TelegramContainer<T>, any Error>) -> ()' to type '(Result<TelegramContainer<T>, any Error>) -> Void' risks causing data races; this is an error in the Swift 6 language mode
129 | return try self.decode(response: response)
130 | })
131 | .whenComplete($0.resume(with: ))
| |- warning: converting a value of type '(__shared sending Result<TelegramContainer<T>, any Error>) -> ()' to type '(Result<TelegramContainer<T>, any Error>) -> Void' risks causing data races; this is an error in the Swift 6 language mode
| `- note: converting a function typed value with a sending parameter to one without risks allowing actor-isolated values to escape their isolation domain as an argument to an invocation of value
132 | }
133 | }
[481/509] Compiling Telegrammer ChatType.swift
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Network/BotClient.swift:131:34: warning: converting a value of type '(__shared sending Result<TelegramContainer<T>, any Error>) -> ()' to type '(Result<TelegramContainer<T>, any Error>) -> Void' risks causing data races; this is an error in the Swift 6 language mode
129 | return try self.decode(response: response)
130 | })
131 | .whenComplete($0.resume(with: ))
| |- warning: converting a value of type '(__shared sending Result<TelegramContainer<T>, any Error>) -> ()' to type '(Result<TelegramContainer<T>, any Error>) -> Void' risks causing data races; this is an error in the Swift 6 language mode
| `- note: converting a function typed value with a sending parameter to one without risks allowing actor-isolated values to escape their isolation domain as an argument to an invocation of value
132 | }
133 | }
[482/509] Compiling Telegrammer FileInfo.swift
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Network/BotClient.swift:131:34: warning: converting a value of type '(__shared sending Result<TelegramContainer<T>, any Error>) -> ()' to type '(Result<TelegramContainer<T>, any Error>) -> Void' risks causing data races; this is an error in the Swift 6 language mode
129 | return try self.decode(response: response)
130 | })
131 | .whenComplete($0.resume(with: ))
| |- warning: converting a value of type '(__shared sending Result<TelegramContainer<T>, any Error>) -> ()' to type '(Result<TelegramContainer<T>, any Error>) -> Void' risks causing data races; this is an error in the Swift 6 language mode
| `- note: converting a function typed value with a sending parameter to one without risks allowing actor-isolated values to escape their isolation domain as an argument to an invocation of value
132 | }
133 | }
[483/509] Compiling Telegrammer InlineQueryResult.swift
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Network/BotClient.swift:131:34: warning: converting a value of type '(__shared sending Result<TelegramContainer<T>, any Error>) -> ()' to type '(Result<TelegramContainer<T>, any Error>) -> Void' risks causing data races; this is an error in the Swift 6 language mode
129 | return try self.decode(response: response)
130 | })
131 | .whenComplete($0.resume(with: ))
| |- warning: converting a value of type '(__shared sending Result<TelegramContainer<T>, any Error>) -> ()' to type '(Result<TelegramContainer<T>, any Error>) -> Void' risks causing data races; this is an error in the Swift 6 language mode
| `- note: converting a function typed value with a sending parameter to one without risks allowing actor-isolated values to escape their isolation domain as an argument to an invocation of value
132 | }
133 | }
[484/509] Compiling Telegrammer InputFile.swift
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Network/BotClient.swift:131:34: warning: converting a value of type '(__shared sending Result<TelegramContainer<T>, any Error>) -> ()' to type '(Result<TelegramContainer<T>, any Error>) -> Void' risks causing data races; this is an error in the Swift 6 language mode
129 | return try self.decode(response: response)
130 | })
131 | .whenComplete($0.resume(with: ))
| |- warning: converting a value of type '(__shared sending Result<TelegramContainer<T>, any Error>) -> ()' to type '(Result<TelegramContainer<T>, any Error>) -> Void' risks causing data races; this is an error in the Swift 6 language mode
| `- note: converting a function typed value with a sending parameter to one without risks allowing actor-isolated values to escape their isolation domain as an argument to an invocation of value
132 | }
133 | }
[485/509] Compiling Telegrammer InputMedia.swift
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Network/BotClient.swift:131:34: warning: converting a value of type '(__shared sending Result<TelegramContainer<T>, any Error>) -> ()' to type '(Result<TelegramContainer<T>, any Error>) -> Void' risks causing data races; this is an error in the Swift 6 language mode
129 | return try self.decode(response: response)
130 | })
131 | .whenComplete($0.resume(with: ))
| |- warning: converting a value of type '(__shared sending Result<TelegramContainer<T>, any Error>) -> ()' to type '(Result<TelegramContainer<T>, any Error>) -> Void' risks causing data races; this is an error in the Swift 6 language mode
| `- note: converting a function typed value with a sending parameter to one without risks allowing actor-isolated values to escape their isolation domain as an argument to an invocation of value
132 | }
133 | }
[486/509] Compiling Telegrammer InputMessageContent.swift
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Network/BotClient.swift:131:34: warning: converting a value of type '(__shared sending Result<TelegramContainer<T>, any Error>) -> ()' to type '(Result<TelegramContainer<T>, any Error>) -> Void' risks causing data races; this is an error in the Swift 6 language mode
129 | return try self.decode(response: response)
130 | })
131 | .whenComplete($0.resume(with: ))
| |- warning: converting a value of type '(__shared sending Result<TelegramContainer<T>, any Error>) -> ()' to type '(Result<TelegramContainer<T>, any Error>) -> Void' risks causing data races; this is an error in the Swift 6 language mode
| `- note: converting a function typed value with a sending parameter to one without risks allowing actor-isolated values to escape their isolation domain as an argument to an invocation of value
132 | }
133 | }
[487/509] Compiling Telegrammer MessageEntityType.swift
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Network/BotClient.swift:131:34: warning: converting a value of type '(__shared sending Result<TelegramContainer<T>, any Error>) -> ()' to type '(Result<TelegramContainer<T>, any Error>) -> Void' risks causing data races; this is an error in the Swift 6 language mode
129 | return try self.decode(response: response)
130 | })
131 | .whenComplete($0.resume(with: ))
| |- warning: converting a value of type '(__shared sending Result<TelegramContainer<T>, any Error>) -> ()' to type '(Result<TelegramContainer<T>, any Error>) -> Void' risks causing data races; this is an error in the Swift 6 language mode
| `- note: converting a function typed value with a sending parameter to one without risks allowing actor-isolated values to escape their isolation domain as an argument to an invocation of value
132 | }
133 | }
[488/509] Compiling Telegrammer MessageOrBool.swift
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Network/BotClient.swift:131:34: warning: converting a value of type '(__shared sending Result<TelegramContainer<T>, any Error>) -> ()' to type '(Result<TelegramContainer<T>, any Error>) -> Void' risks causing data races; this is an error in the Swift 6 language mode
129 | return try self.decode(response: response)
130 | })
131 | .whenComplete($0.resume(with: ))
| |- warning: converting a value of type '(__shared sending Result<TelegramContainer<T>, any Error>) -> ()' to type '(Result<TelegramContainer<T>, any Error>) -> Void' risks causing data races; this is an error in the Swift 6 language mode
| `- note: converting a function typed value with a sending parameter to one without risks allowing actor-isolated values to escape their isolation domain as an argument to an invocation of value
132 | }
133 | }
[489/509] Compiling Telegrammer ParseMode.swift
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Network/BotClient.swift:131:34: warning: converting a value of type '(__shared sending Result<TelegramContainer<T>, any Error>) -> ()' to type '(Result<TelegramContainer<T>, any Error>) -> Void' risks causing data races; this is an error in the Swift 6 language mode
129 | return try self.decode(response: response)
130 | })
131 | .whenComplete($0.resume(with: ))
| |- warning: converting a value of type '(__shared sending Result<TelegramContainer<T>, any Error>) -> ()' to type '(Result<TelegramContainer<T>, any Error>) -> Void' risks causing data races; this is an error in the Swift 6 language mode
| `- note: converting a function typed value with a sending parameter to one without risks allowing actor-isolated values to escape their isolation domain as an argument to an invocation of value
132 | }
133 | }
[490/509] Compiling Telegrammer PassportElementError.swift
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Network/BotClient.swift:131:34: warning: converting a value of type '(__shared sending Result<TelegramContainer<T>, any Error>) -> ()' to type '(Result<TelegramContainer<T>, any Error>) -> Void' risks causing data races; this is an error in the Swift 6 language mode
129 | return try self.decode(response: response)
130 | })
131 | .whenComplete($0.resume(with: ))
| |- warning: converting a value of type '(__shared sending Result<TelegramContainer<T>, any Error>) -> ()' to type '(Result<TelegramContainer<T>, any Error>) -> Void' risks causing data races; this is an error in the Swift 6 language mode
| `- note: converting a function typed value with a sending parameter to one without risks allowing actor-isolated values to escape their isolation domain as an argument to an invocation of value
132 | }
133 | }
[491/509] Compiling Telegrammer ReplyMarkup.swift
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Network/BotClient.swift:131:34: warning: converting a value of type '(__shared sending Result<TelegramContainer<T>, any Error>) -> ()' to type '(Result<TelegramContainer<T>, any Error>) -> Void' risks causing data races; this is an error in the Swift 6 language mode
129 | return try self.decode(response: response)
130 | })
131 | .whenComplete($0.resume(with: ))
| |- warning: converting a value of type '(__shared sending Result<TelegramContainer<T>, any Error>) -> ()' to type '(Result<TelegramContainer<T>, any Error>) -> Void' risks causing data races; this is an error in the Swift 6 language mode
| `- note: converting a function typed value with a sending parameter to one without risks allowing actor-isolated values to escape their isolation domain as an argument to an invocation of value
132 | }
133 | }
[492/509] Compiling Telegrammer TelegramContainer.swift
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Network/BotClient.swift:131:34: warning: converting a value of type '(__shared sending Result<TelegramContainer<T>, any Error>) -> ()' to type '(Result<TelegramContainer<T>, any Error>) -> Void' risks causing data races; this is an error in the Swift 6 language mode
129 | return try self.decode(response: response)
130 | })
131 | .whenComplete($0.resume(with: ))
| |- warning: converting a value of type '(__shared sending Result<TelegramContainer<T>, any Error>) -> ()' to type '(Result<TelegramContainer<T>, any Error>) -> Void' risks causing data races; this is an error in the Swift 6 language mode
| `- note: converting a function typed value with a sending parameter to one without risks allowing actor-isolated values to escape their isolation domain as an argument to an invocation of value
132 | }
133 | }
[493/509] Compiling Telegrammer TelegramEncodables.swift
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Network/BotClient.swift:131:34: warning: converting a value of type '(__shared sending Result<TelegramContainer<T>, any Error>) -> ()' to type '(Result<TelegramContainer<T>, any Error>) -> Void' risks causing data races; this is an error in the Swift 6 language mode
129 | return try self.decode(response: response)
130 | })
131 | .whenComplete($0.resume(with: ))
| |- warning: converting a value of type '(__shared sending Result<TelegramContainer<T>, any Error>) -> ()' to type '(Result<TelegramContainer<T>, any Error>) -> Void' risks causing data races; this is an error in the Swift 6 language mode
| `- note: converting a function typed value with a sending parameter to one without risks allowing actor-isolated values to escape their isolation domain as an argument to an invocation of value
132 | }
133 | }
[494/509] Compiling Telegrammer Updater.swift
/Users/admin/builder/spi-builder-workspace/Sources/Telegrammer/Network/BotClient.swift:131:34: warning: converting a value of type '(__shared sending Result<TelegramContainer<T>, any Error>) -> ()' to type '(Result<TelegramContainer<T>, any Error>) -> Void' risks causing data races; this is an error in the Swift 6 language mode
129 | return try self.decode(response: response)
130 | })
131 | .whenComplete($0.resume(with: ))
| |- warning: converting a value of type '(__shared sending Result<TelegramContainer<T>, any Error>) -> ()' to type '(Result<TelegramContainer<T>, any Error>) -> Void' risks causing data races; this is an error in the Swift 6 language mode
| `- note: converting a function typed value with a sending parameter to one without risks allowing actor-isolated values to escape their isolation domain as an argument to an invocation of value
132 | }
133 | }
[495/526] Emitting module DemoSchedulerBot
[496/526] Emitting module DemoWebhooksLocally
[497/526] Compiling DemoWebhooksLocally main.swift
[498/526] Emitting module DemoEchoBot
[499/526] Compiling DemoEchoBot main.swift
[500/526] Compiling DemoSpellCheckerBot main.swift
[501/526] Compiling DemoHelloBot NewMemberHandler.swift
[502/526] Compiling DemoHelloBot main.swift
[503/526] Emitting module DemoHelloBot
[503/526] Write Objects.LinkFileList
[506/526] Compiling DemoSchedulerBot main.swift
[506/526] Write Objects.LinkFileList
[508/526] Compiling DemoSpellCheckerBot SpellChecker.swift
[509/526] Compiling DemoSpellCheckerBot YaSpellCheck.swift
[510/526] Compiling DemoSpellCheckerBot Array+Helper.swift
[511/526] Compiling DemoSpellCheckerBot YaSpellChecker.swift
[512/526] 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.
147 | messageId: message.messageId,
148 | text: text,
149 | parseMode: .markdown,
| |- warning: 'markdown' is deprecated: This is a legacy mode, retained for backward compatibility.
| `- note: use 'markdownV2' instead
150 | replyMarkup: markup)
151 | try bot.editMessageText(params: params)
/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.
155 | let params = Bot.SendMessageParams(chatId: .chat(message.chat.id),
156 | text: text,
157 | parseMode: .markdown,
| |- warning: 'markdown' is deprecated: This is a legacy mode, retained for backward compatibility.
| `- note: use 'markdownV2' instead
158 | replyMarkup: markup)
159 | try self.bot.sendMessage(params: params)
[513/526] Compiling DemoSpellCheckerBot YaSpellFlow.swift
[514/526] Emitting module DemoSpellCheckerBot
[514/526] Write Objects.LinkFileList
[516/526] Linking WebhooksLocally
[517/526] Linking SchedulerBot
[518/526] Linking EchoBot
[519/526] Linking HelloBot
[520/526] Linking SpellCheckerBot
[521/526] Applying WebhooksLocally
[522/526] Applying SchedulerBot
[523/526] Applying EchoBot
[524/526] Applying HelloBot
[525/526] Applying SpellCheckerBot
Build complete! (13.69s)
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.15"
}
],
"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+banChatMember.swift",
"Bot/Telegram/Methods/Bot+close.swift",
"Bot/Telegram/Methods/Bot+copyMessage.swift",
"Bot/Telegram/Methods/Bot+createChatInviteLink.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+deleteMyCommands.swift",
"Bot/Telegram/Methods/Bot+deleteStickerFromSet.swift",
"Bot/Telegram/Methods/Bot+deleteWebhook.swift",
"Bot/Telegram/Methods/Bot+editChatInviteLink.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+getChatMemberCount.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+logOut.swift",
"Bot/Telegram/Methods/Bot+pinChatMessage.swift",
"Bot/Telegram/Methods/Bot+promoteChatMember.swift",
"Bot/Telegram/Methods/Bot+restrictChatMember.swift",
"Bot/Telegram/Methods/Bot+revokeChatInviteLink.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+unpinAllChatMessages.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/BotCommandScope.swift",
"Bot/Telegram/Models/BotCommandScopeAllChatAdministrators.swift",
"Bot/Telegram/Models/BotCommandScopeAllGroupChats.swift",
"Bot/Telegram/Models/BotCommandScopeAllPrivateChats.swift",
"Bot/Telegram/Models/BotCommandScopeChat.swift",
"Bot/Telegram/Models/BotCommandScopeChatAdministrators.swift",
"Bot/Telegram/Models/BotCommandScopeChatMember.swift",
"Bot/Telegram/Models/BotCommandScopeDefault.swift",
"Bot/Telegram/Models/CallbackGame.swift",
"Bot/Telegram/Models/CallbackQuery.swift",
"Bot/Telegram/Models/Chat.swift",
"Bot/Telegram/Models/ChatInviteLink.swift",
"Bot/Telegram/Models/ChatLocation.swift",
"Bot/Telegram/Models/ChatMember.swift",
"Bot/Telegram/Models/ChatMemberAdministrator.swift",
"Bot/Telegram/Models/ChatMemberBanned.swift",
"Bot/Telegram/Models/ChatMemberLeft.swift",
"Bot/Telegram/Models/ChatMemberMember.swift",
"Bot/Telegram/Models/ChatMemberOwner.swift",
"Bot/Telegram/Models/ChatMemberRestricted.swift",
"Bot/Telegram/Models/ChatMemberUpdated.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/InputInvoiceMessageContent.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/MessageAutoDeleteTimerChanged.swift",
"Bot/Telegram/Models/MessageEntity.swift",
"Bot/Telegram/Models/MessageId.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/ProximityAlertTriggered.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/VoiceChatEnded.swift",
"Bot/Telegram/Models/VoiceChatParticipantsInvited.swift",
"Bot/Telegram/Models/VoiceChatScheduled.swift",
"Bot/Telegram/Models/VoiceChatStarted.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.