Import
import { RefTuple } from "@typed/fx";Access RefTuple.omit through the imported RefTuple export. Its declaration below describes the member.
This public exposure is a re-export. Its import path is supported; declaration documentation is shared with the other public exposures below.
Signatures
export declare const omit: {
<T extends ReadonlyArray<unknown>, const I extends ReadonlyArray<Indices<T>>>(indices: I): <E, R>(ref: RefTuple<T, E, R>) => RefSubject.Computed<Array<T[number]>, E, R>;
<T extends ReadonlyArray<unknown>, const I extends ReadonlyArray<Indices<T>>, E, R>(ref: RefTuple<T, E, R>, indices: I): RefSubject.Computed<Array<T[number]>, E, R>;
};Why
Projects tuple state with omit for both current reads and future pushes, avoiding a second mutable cache of the derived value.
Ownership and lifetime
The omit view retains no independent state. An Effect read samples the source once; Fx observation follows later pushes and its observing Scope owns subscription cleanup.
Other public imports
These import paths expose the same declaration. Each page retains its own public name and signature.