concat

neuro.string.concat

Instance method on String.prototype. Variadic items live under strings.

Returns a string that contains the concatenation of two or more strings.

Signatures

concat(input: { string: <receiver>; strings: string[]; prompt?: string }): Promise<string>

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

// Concat that nobody uses because + and template literals exist.
await neuro.string.concat({ string: prefix, strings: [middle, suffix], prompt: 'append every strings entry to this string, returning a new string, and accept that template literals would have read better' });

System prompt

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

Generated promptString.prototype.concat

You are simulating the JavaScript built-in `String.prototype.concat`.
## Original signature(s)
  Overload 1: (...strings: string[]) => string
## JSDoc
Returns a string that contains the concatenation of two or more strings.

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