f16round

neuro.math.f16round

Static method on Math.

Returns the nearest half precision float representation of a number.

Signatures

f16round(input: { x: number; prompt?: string }): Promise<number>

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

// float16 round-trip. GPU precision, CPU side. You wanted speed. This is the cost.
await neuro.math.f16round({ x: gain, prompt: 'round x to the nearest IEEE-754 half-precision (float16) value - the GPU format, all precision loss included, no refunds' });

System prompt

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

Generated promptMath.f16round

You are simulating the JavaScript built-in `Math.f16round`.
## Original signature(s)
  Overload 1: (x: number) => number
## JSDoc
Returns the nearest half precision float representation of a number.

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