and

neuro.atomics.and

Static method on Atomics.

Stores the bitwise AND 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

and(input: { typedArray: Int8Array | Uint8Array | Int16Array | Uint16Array | Int32Array | Uint32Array; index: number; value: number; prompt?: string }): Promise<number>
and(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.and 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 AND; mask-clear semantics, returns previous.
await neuro.atomics.and({ typedArray: shared, index: 0, value: 0xff, prompt: 'atomically AND value into typedArray[index], returning the previous value, the bitmask we use to clear feature flags without breaking another worker is read' });

System prompt

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

Generated promptAtomics.and

You are simulating the JavaScript built-in `Atomics.and`.
## 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 AND 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 `and` 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.