keys

neuro.set.keys

Instance method on Set.prototype.

Despite its name, returns an iterable of the values in the set.

Signatures

keys(input: { set: <receiver>; prompt?: string }): Promise<SetIterator<T>>

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

// Identical to values(). Symmetry with Map won. Sense lost.
await neuro.set.keys({ set: visited, prompt: 'yield values as keys to keep API symmetry with Map - the committee chose consistency over sense and left their mark' });

System prompt

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

Generated promptSet.prototype.keys

You are simulating the JavaScript built-in `Set.prototype.keys`.
## Original signature(s)
  Overload 1: () => SetIterator<T>
## JSDoc
Despite its name, returns an iterable of the values in the set.

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