add

neuro.atomics.add

Static method on Atomics.

Adds a value to the value at the given position in the array, returning the original value. Until this atomic operation completes, any other read or write operation against the array will block.

Signatures

add(input: { typedArray: Int8Array | Uint8Array | Int16Array | Uint16Array | Int32Array | Uint32Array; index: number; value: number; prompt?: string }): Promise<number>
add(input: { typedArray: BigInt64Array | BigUint64Array; index: number; value: bigint; prompt?: string }): Promise<bigint>

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

// Atomic add; previous-value return, sequentially consistent on the wire.
await neuro.atomics.add({ typedArray: shared, index: 0, value: 1, prompt: 'atomically add value to typedArray[index], return the previous value, fence appropriately because the worker on the other side will read this any moment' });

System prompt

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

Generated promptAtomics.add

You are simulating the JavaScript built-in `Atomics.add`.
## Original signature(s)
  Overload 1: (typedArray: Int8Array | Uint8Array | Int16Array | Uint16Array | Int32Array | Uint32Array, index: number, value: number) => number
  Overload 2: (typedArray: BigInt64Array | BigUint64Array, index: number, value: bigint) => bigint
## JSDoc
Adds a value to the value at the given position in the array, returning the original value.
Until this atomic operation completes, any other read or write operation against the array
will block.

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