fromAsync
neuro.array.fromAsync
Section titled “neuro.array.fromAsync”Static method on Array.
Creates an array from an async iterator or iterable object.
Signatures
Section titled “Signatures”fromAsync(input: { iterableOrArrayLike: AsyncIterable<T> | Iterable<T | PromiseLike<T>> | ArrayLike<T | PromiseLike<T>>; prompt?: string }): Promise<Promise<T[]>>fromAsync(input: { iterableOrArrayLike: AsyncIterable<T> | Iterable<T> | ArrayLike<T>; mapFn?: (value: Awaited<T>; index: number) => U; thisArg?: any; prompt?: string }): Promise<Promise<Awaited<U>[]>>The prompt field is optional. When omitted (or set to an empty string)
the wrapper falls back to the native Array.fromAsync and returns a
resolved Promise without contacting the LLM. When present, the LLM is given
the original arguments plus your prompt and is asked to behave like the
original method.
Example
Section titled “Example”import { configureClient, neuro } from 'neuro-ts';
configureClient({ apiKey: process.env.OPENAI_API_KEY });
// Like Array.from but awaits; the timeout boundary decides retroactively which values got included.await neuro.array.fromAsync({ iterableOrArrayLike: stream, prompt: 'collect from an async iterable in arrival order, await each value, and let the timeout decide which calls counted' });System prompt
Section titled “System prompt”The exact system prompt the SDK sends to your model when you provide a
prompt field:
Array.fromAsyncYou are simulating the JavaScript built-in `Array.fromAsync`.
## Original signature(s)
Overload 1: (iterableOrArrayLike: AsyncIterable<T> | Iterable<T | PromiseLike<T>> | ArrayLike<T | PromiseLike<T>>) => Promise<T[]>
Overload 2: (iterableOrArrayLike: AsyncIterable<T> | Iterable<T> | ArrayLike<T>, mapFn?: (value: Awaited<T>, index: number) => U, thisArg?: any) => Promise<Awaited<U>[]>
## JSDoc
Creates an array from an async iterator or iterable object.
## How to respond
- Behave EXACTLY as the original `fromAsync` would, but use the user's intent to choose any callback / comparator / transform logic that the original would normally accept as an argument.
- Strictly preserve the original return type and shape.
- Output ONLY the JSON-encoded return value of the function call.
- Do NOT include explanations, prose, comments, or markdown fences.
- If the function would return `undefined`, output the literal string `undefined`.
- For Date / RegExp / Map / Set / TypedArray returns, output an object of the form { "__type": "Date" | "RegExp" | "Map" | "Set" | "<TypedArrayName>", ... } so the SDK can rehydrate it.