/**
 * `repeat=` together with `order="sequential"`.
 *
 * A FIXED repeat is a feature and lives in the engines: the row's N values walk
 * the source, element k of row r taking source index `r * N + k`. At `repeat="1"`
 * that is exactly what `order="sequential"` alone has always done, which is what
 * makes it the right generalisation rather than a second meaning.
 *
 * A RANGED repeat is what stays refused, and the reason is the stride. A walk
 * advances by a fixed number of values per row; a row whose length is decided by
 * the length quota has no such number, and any answer would make row r depend on
 * how many values the rows before it happened to take — which is precisely what
 * every engine here is built not to do.
 *
 * ── What it used to be ───────────────────────────────────────────────────────
 * Both spellings were refused, because both produced different data on different
 * engines:
 *
 *   <gen type="text" value="created,paid,shipped,delivered" repeat="4" order="sequential"/>
 *
 *   engine 1        four elements per row, all of them the SAME value, and the
 *                   value did not advance from row to row either
 *   engines 2 and 3 the repeat list was dropped: ONE value per row, walking
 *
 * `check` called that document valid, so the author got a column of data that
 * looked plausible, was wrong, and was wrong DIFFERENTLY depending on which
 * engine answered.
 */
import type { Diagnostic } from '../errors/index.js';
import type { OpenCloseElementContext, SelfClosingElementContext } from '../generated/TDCParser.js';
export declare function checkSequentialRepeat(gen: OpenCloseElementContext | SelfClosingElementContext, diagnostics: Diagnostic[]): void;
//# sourceMappingURL=sequential-repeat.d.ts.map