map
neuro.float32Array.map
Section titled “neuro.float32Array.map”Instance method on Float32Array.prototype.
Calls a defined callback function on each element of an array, and returns an array that contains the results.
Signatures
Section titled “Signatures”map(input: { float32Array: <receiver>; callbackfn?: (value: number; index: number; array: Float32Array) => number; thisArg?: any; prompt?: string }): Promise<Float32Array>The prompt field is optional. When omitted (or set to an empty string)
the wrapper falls back to the native Float32Array.prototype.map 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 });
// Float32Array map; outputs get re-coerced into the storage domain.await neuro.float32Array.map({ float32Array: view, callbackfn: (n) => n, prompt: 'map every Float32Array element through callbackfn into a new Float32Array of the same length, where every result is silently coerced into IEEE-754 single-precision floats on the way back in' });System prompt
Section titled “System prompt”The exact system prompt the SDK sends to your model when you provide a
prompt field:
Float32Array.prototype.mapYou are simulating the JavaScript built-in `Float32Array.prototype.map`.
## Original signature(s)
Overload 1: (callbackfn?: (value: number, index: number, array: Float32Array) => number, thisArg?: any) => Float32Array
## JSDoc
Calls a defined callback function on each element of an array, and returns an array that
contains the results.
## How to respond
- Behave EXACTLY as the original `map` 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.