RunHyperlinkConfig<T, A, E>Configuration for RunHyperlink.make — local scoped handle, no RPC.
export interface interface RunHyperlinkConfig<T, A, E>Configuration for
RunHyperlink.make
— local scoped handle, no RPC.
RunHyperlinkConfig<function (type parameter) T in RunHyperlinkConfig<T, A, E>T, function (type parameter) A in RunHyperlinkConfig<T, A, E>A, function (type parameter) E in RunHyperlinkConfig<T, A, E>E> {
readonly RunHyperlinkConfig<T, A, E>.name?: string | undefinedname?: string;
readonly RunHyperlinkConfig<T, A, E>.effect: (input: T) => Effect.Effect<A, E>effect: (input: Tinput: function (type parameter) T in RunHyperlinkConfig<T, A, E>T) => import EffectEffect.interface Effect<out A, out E = never, out R = never>The Effect interface defines a value that lazily describes a workflow or
job. The workflow requires some context R, and may fail with an error of
type E, or succeed with a value of type A.
When to use
Use when you need to represent a lazy, composable workflow that can require
services, fail with a typed error, or succeed with a typed value.
Details
Effect values model resourceful interaction with the outside world,
including synchronous, asynchronous, concurrent, and parallel interaction.
They use a fiber-based concurrency model, with built-in support for
scheduling, fine-grained interruption, structured concurrency, and high
scalability.
To run an Effect value, you need a Runtime, which is a type that is
capable of executing Effect values.
Effect<function (type parameter) A in RunHyperlinkConfig<T, A, E>A, function (type parameter) E in RunHyperlinkConfig<T, A, E>E>;
readonly RunHyperlinkConfig<T, A, E>.concurrency?: number | undefinedconcurrency?: number;
}