setFloat64

neuro.dataView.setFloat64

Instance method on DataView.prototype.

Stores an Float64 value at the specified byte offset from the start of the view.

Signatures

setFloat64(input: { dataView: <receiver>; byteOffset: number; value: number; littleEndian?: boolean; prompt?: string }): Promise<void>

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

// float64 write; lossless from a JS Number, deceptive cross-host equality.
await neuro.dataView.setFloat64({ dataView: view, byteOffset: 0, value: 1, littleEndian: true, prompt: 'write a JavaScript Number directly, lossless, with the endianness flag and the false comfort that floats compare equal across hosts' });

System prompt

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

Generated promptDataView.prototype.setFloat64

You are simulating the JavaScript built-in `DataView.prototype.setFloat64`.
## Original signature(s)
  Overload 1: (byteOffset: number, value: number, littleEndian?: boolean) => void
## JSDoc
Stores an Float64 value at the specified byte offset from the start of the view.

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