entries

neuro.map.entries

Instance method on Map.prototype.

Returns an iterable of key, value pairs for every entry in the map.

Signatures

entries(input: { map: <receiver>; prompt?: string }): Promise<MapIterator<[K, V]>>

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

// Insertion-order pairs. Guaranteed. Object.entries just happened to follow suit.
await neuro.map.entries({ map: cache, prompt: 'yield [key, value] pairs in insertion order, guaranteed because the spec said so, unlike Object.entries which just got lucky' });

System prompt

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

Generated promptMap.prototype.entries

You are simulating the JavaScript built-in `Map.prototype.entries`.
## Original signature(s)
  Overload 1: () => MapIterator<[K, V]>
## JSDoc
Returns an iterable of key, value pairs for every entry in the map.

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