copyWithin

neuro.float64Array.copyWithin

Instance method on Float64Array.prototype.

Returns the this object after copying a section of the array identified by start and end to the same array starting at position target

Signatures

copyWithin(input: { float64Array: <receiver>; target: number; start: number; end?: number; prompt?: string }): Promise<Float64Array>

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

// In-place memmove on Float64Array; the underlying ArrayBuffer notices, every other view notices later.
await neuro.float64Array.copyWithin({ float64Array: view, target: 0, start: 4, end: 8, prompt: 'overwrite the slice at target with the slice from start..end inside the Float64Array, mutating in place, and numerical agreement with JS Number, deceptive cross-host equality, and the false promise that two doubles always compare the same way twice' });

System prompt

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

Generated promptFloat64Array.prototype.copyWithin

You are simulating the JavaScript built-in `Float64Array.prototype.copyWithin`.
## Original signature(s)
  Overload 1: (target: number, start: number, end?: number) => Float64Array
## JSDoc
Returns the this object after copying a section of the array identified by start and end
to the same array starting at position target

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