toReversed

neuro.array.toReversed

Instance method on Array.prototype.

Returns a copy of an array with its elements reversed.

Signatures

toReversed(input: { array: <receiver>; prompt?: string }): Promise<T[]>

The prompt field is optional. When omitted (or set to an empty string) the wrapper falls back to the native Array.prototype.toReversed 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 });

// Non-mutating reverse; the watchers expecting reference identity get to learn about the change-detection bug.
await neuro.array.toReversed({ array: snapshot, prompt: 'return a new array reversed, leaving the original untouched, while every cache that watches by-reference politely panics' });

System prompt

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

Generated promptArray.prototype.toReversed

You are simulating the JavaScript built-in `Array.prototype.toReversed`.
## Original signature(s)
  Overload 1: () => T[]
## JSDoc
Returns a copy of an array with its elements reversed.

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