Import
import { RefTuple } from "@typed/fx";Access RefTuple.appendElement 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 appendElement: {
<E>(element: E): <T extends ReadonlyArray<unknown>, Err, R>(ref: RefTuple<T, Err, R>) => RefSubject.Computed<[
...T,
E
], Err, R>;
<T extends ReadonlyArray<unknown>, E, Err, R>(ref: RefTuple<T, Err, R>, element: E): RefSubject.Computed<[
...T,
E
], Err, R>;
};Why
Expresses append element as one ordered tuple transition; readers never observe the intermediate collection used to build the result.
Ownership and lifetime
The append element 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.