(items: T | ReadonlyArray<T>, level?: number | string): Effect.Effect<
void,
EEnqueue,
R
>models
Source src/internal/customQueueHyperlink.ts:876 lines
export interface interface CustomQueueEnqueue<T, EEnqueue = never, R = never>CustomQueueEnqueue<function (type parameter) T in CustomQueueEnqueue<T, EEnqueue = never, R = never>T, function (type parameter) EEnqueue in CustomQueueEnqueue<T, EEnqueue = never, R = never>EEnqueue = never, function (type parameter) R in CustomQueueEnqueue<T, EEnqueue = never, R = never>R = never> {
(
items: T | readonly T[]items: function (type parameter) T in CustomQueueEnqueue<T, EEnqueue = never, R = never>T | interface ReadonlyArray<T>ReadonlyArray<function (type parameter) T in CustomQueueEnqueue<T, EEnqueue = never, R = never>T>,
level: string | number | undefinedlevel?: number | string,
): 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<void, function (type parameter) EEnqueue in CustomQueueEnqueue<T, EEnqueue = never, R = never>EEnqueue, function (type parameter) R in CustomQueueEnqueue<T, EEnqueue = never, R = never>R>;
}