Instance Methodasync-kit 1.20.0AsyncKit->NIOCore
makeFutureWithTask(_:)
EventLoopGroup+Concurrency.swift:25func makeFutureWithTask<Value>(_ body: @escaping () async throws -> Value) -> EventLoopFuture<Value> func makeFutureWithTask<Value>(_ body: @escaping () async throws -> Value) -> EventLoopFuture<Value> s7NIOCore14EventLoopGroupP8AsyncKitE18makeFutureWithTaskyAA0bcH0Cyqd__Gqd__yYaYbKclF What are these?5SYNJimport NIOCoreThe core abstractions that make up SwiftNIO.
import AsyncKitProvides a set of utilities for working with EventLoopFutures and other pre-Concurrency support APIs.
protocol EventLoopGroup : AnyObject, _NIOPreconcurrencySendableProvides an endless stream of EventLoops to use.
final class EventLoopFuture<Value>Holder for a result that will be provided later.
func future() -> EventLoopFuture<Void> Creates a new, succeeded EventLoopFuture from the worker’s event loop with a Void value.
func future<T>(_ value: T) -> EventLoopFuture<T> Creates a new, succeeded EventLoopFuture from the worker’s event loop.
func future<T>(error: Error) -> EventLoopFuture<T> Creates a new, failed EventLoopFuture from the worker’s event loop.
func future<T>(result: Result<T, Error>) -> EventLoopFuture<T> Creates a new Future from the worker’s event loop, succeeded or failed based on the input Result.
func tryFuture<T>(_ work: @escaping () throws -> T) -> EventLoopFuture<T> An alternate name for this would be future(catching:), but with that name, trailing closure syntax just looks like el.future { ... }, which does not indicate to readers of the code that it is the error-capturing version. Since such an indication is highly desirable, a slightly less idiomatic name is used instead.
func performWithTask<Value>(_ body: @escaping () async throws -> Value) -> EventLoopFuture<Value> Run the async function body on an event loop in this group and return its result as an EventLoopFuture.