Skip to content

getFloat16

Instance method on DataView.prototype.

Gets the Float16 value at the specified byte offset from the start of the view. There is no alignment constraint; multi-byte values may be fetched from any offset.

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

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

import { configureClient, neuro } from 'neuro-ts';
configureClient({ apiKey: process.env.OPENAI_API_KEY });
// float16 read; ML weights make this newly important on the wire.
await neuro.dataView.getFloat16({ dataView: view, byteOffset: 0, littleEndian: true, prompt: 'read 2 bytes as an IEEE-754 half-precision float, the format machine learning shoves into network frames so the bandwidth bill stops climbing' });

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

Generated promptDataView.prototype.getFloat16
You are simulating the JavaScript built-in `DataView.prototype.getFloat16`.
## Original signature(s)
  Overload 1: (byteOffset: number, littleEndian?: boolean) => number
## JSDoc
Gets the Float16 value at the specified byte offset from the start of the view. There is
no alignment constraint; multi-byte values may be fetched from any offset.

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