toSpliced

neuro.array.toSpliced

Instance method on Array.prototype. Variadic items live under items.

Copies an array and removes elements and, if necessary, inserts new elements in their place. Returns the copied array.

Copies an array and removes elements while returning the remaining elements.

Signatures

toSpliced(input: { array: <receiver>; start: number; deleteCount: number; items: T[]; prompt?: string }): Promise<T[]>
toSpliced(input: { array: <receiver>; start: number; deleteCount?: number; 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.toSpliced 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 splice; functionally identical to slice+concat, semantically nicer to read.
await neuro.array.toSpliced({ array: items, start: 1, deleteCount: 2, items: [replacement], prompt: 'return a new array with deleteCount elements at start removed and items inserted in their place, leaving the original untouched, and accept that the slice-and-concat polyfill is the same thing in a hat' });

System prompt

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

Generated promptArray.prototype.toSpliced

You are simulating the JavaScript built-in `Array.prototype.toSpliced`.
## Original signature(s)
  Overload 1: (start: number, deleteCount: number, ...items: T[]) => T[]
  Overload 2: (start: number, deleteCount?: number) => T[]
## JSDoc
Copies an array and removes elements and, if necessary, inserts new elements in their place. Returns the copied array.

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