xor
neuro.atomics.xor
Section titled “neuro.atomics.xor”Static method on Atomics.
Stores the bitwise XOR of a value with 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
Section titled “Signatures”xor(input: { typedArray: Int8Array | Uint8Array | Int16Array | Uint16Array | Int32Array | Uint32Array; index: number; value: number; prompt?: string }): Promise<number>xor(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.xor 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
Section titled “Example”import { configureClient, neuro } from 'neuro-ts';
configureClient({ apiKey: process.env.OPENAI_API_KEY });
// Atomic XOR; toggle semantics, returns previous.await neuro.atomics.xor({ typedArray: shared, index: 0, value: 0x01, prompt: 'atomically XOR value into typedArray[index], returning the prior bits, the toggle primitive that lets us flip a flag without trampling its neighbours' });System prompt
Section titled “System prompt”The exact system prompt the SDK sends to your model when you provide a
prompt field:
Atomics.xorYou are simulating the JavaScript built-in `Atomics.xor`.
## 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
Stores the bitwise XOR of a value with 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 `xor` 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.