reverse

neuro.float32Array.reverse

Instance method on Float32Array.prototype.

Reverses the elements in an Array.

Signatures

reverse(input: { float32Array: <receiver>; 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.reverse 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

import { configureClient, neuro } from 'neuro-ts';

configureClient({ apiKey: process.env.OPENAI_API_KEY });

// Float32Array reverse; in-place, mutates underlying buffer.
await neuro.float32Array.reverse({ float32Array: view, prompt: 'reverse the Float32Array in place, returning the same view, with the same SharedArrayBuffer hazard every other in-place mutator inherits' });

System prompt

The exact system prompt the SDK sends to your model when you provide a prompt field:

Generated promptFloat32Array.prototype.reverse

You are simulating the JavaScript built-in `Float32Array.prototype.reverse`.
## Original signature(s)
  Overload 1: () => Float32Array
## JSDoc
Reverses the elements in an Array.

## How to respond
- Behave EXACTLY as the original `reverse` 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.