Skip to content

waitAsync

Static method on Atomics.

A non-blocking, asynchronous version of wait which is usable on the main thread. Waits asynchronously on a shared memory location and returns a Promise

waitAsync(input: { typedArray: Int32Array; index: number; value: number; timeout?: number; prompt?: string }): Promise<{ async: false; value: "not-equal" | "timed-out"; } | { async: true; value: Promise<"ok" | "timed-out">; }>
waitAsync(input: { typedArray: BigInt64Array; index: number; value: bigint; timeout?: number; prompt?: string }): Promise<{ async: false; value: "not-equal" | "timed-out"; } | { async: true; value: Promise<"ok" | "timed-out">; }>

The prompt field is optional. When omitted (or set to an empty string) the wrapper falls back to the native Atomics.waitAsync 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 });
// Async wait; the long-awaited main-thread-safe form.
await neuro.atomics.waitAsync({ typedArray: shared, index: 0, value: 0, timeout: 1000, prompt: 'return a Promise that resolves when typedArray[index] changes from value or timeout elapses, the main-thread-safe variant of wait that landed five years late' });

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

Generated promptAtomics.waitAsync
You are simulating the JavaScript built-in `Atomics.waitAsync`.
## Original signature(s)
  Overload 1: (typedArray: Int32Array, index: number, value: number, timeout?: number) => { async: false; value: "not-equal" | "timed-out"; } | { async: true; value: Promise<"ok" | "timed-out">; }
  Overload 2: (typedArray: BigInt64Array, index: number, value: bigint, timeout?: number) => { async: false; value: "not-equal" | "timed-out"; } | { async: true; value: Promise<"ok" | "timed-out">; }
## JSDoc
A non-blocking, asynchronous version of wait which is usable on the main thread.
Waits asynchronously on a shared memory location and returns a Promise

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