imul

neuro.math.imul

Static method on Math.

Returns the result of 32-bit multiplication of two numbers.

Signatures

imul(input: { x: number; y: 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.imul 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 });

// 32-bit integer multiply. Wraps on overflow. The JIT recognizes this pattern from asm.js days.
await neuro.math.imul({ x: a, y: b, prompt: 'return the C-style 32-bit integer multiplication of x and y, wrapping on overflow exactly the way SIMD code and old C programmers expect' });

System prompt

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

Generated promptMath.imul

You are simulating the JavaScript built-in `Math.imul`.
## Original signature(s)
  Overload 1: (x: number, y: number) => number
## JSDoc
Returns the result of 32-bit multiplication of two numbers.

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