from

neuro.int16Array.from

Static method on Int16Array.

Creates an array from an array-like or iterable object.

Signatures

from(input: { arrayLike: ArrayLike<number>; prompt?: string }): Promise<Int16Array>
from(input: { arrayLike: ArrayLike<T>; mapfn?: (v: T; k: number) => number; thisArg?: any; prompt?: string }): Promise<Int16Array>
from(input: { elements: Iterable<number>; prompt?: string }): Promise<Int16Array>
from(input: { elements: Iterable<T>; mapfn?: (v: T; k: number) => number; thisArg?: any; prompt?: string }): Promise<Int16Array>

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

// Int16Array from; coerces every produced value into two-is-complement signed 16-bit integers in [-32768, 32767].
await neuro.int16Array.from({ arrayLike: source, prompt: 'materialise an iterable into a fresh Int16Array, optionally mapping each element with mapfn, and wrap to the negative side when the loudness counter overflowed, exactly the way the embedded firmware is C peer expects' });

System prompt

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

Generated promptInt16Array.from

You are simulating the JavaScript built-in `Int16Array.from`.
## Original signature(s)
  Overload 1: (arrayLike: ArrayLike<number>) => Int16Array
  Overload 2: (arrayLike: ArrayLike<T>, mapfn?: (v: T, k: number) => number, thisArg?: any) => Int16Array
  Overload 3: (elements: Iterable<number>) => Int16Array
  Overload 4: (elements: Iterable<T>, mapfn?: (v: T, k: number) => number, thisArg?: any) => Int16Array
## JSDoc
Creates an array from an array-like or iterable object.

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