/**
 * The key two TEXTS share when `==` calls them equal.
 *
 * `==` between two texts has one rule that is not plain string equality: if both
 * read as whole numbers, they are compared as whole numbers. So `"01" == "1"` is
 * true, and `"0" == "00"` is true.
 *
 * Most of the engine never needs this, because it evaluates the expression. Two
 * places do not evaluate it and must still agree with it:
 *
 * - a `<gen type="pool" filter="field == Column">` is BUCKETED, so a row costs a
 *   map lookup instead of a walk over every member;
 * - TDC225 asks, before the run, whether the two sides can ever overlap.
 *
 * Both compared raw text, and both were therefore wrong about the same configs.
 * Measured on a pool whose `code` holds `01,02,03` against a column producing
 * `1,2,3`:
 *
 *     filter="code == Want"            check REFUSED it: "can never match"
 *     filter="code == Want && 1 == 1"  matched every row
 *
 * The second is the same question with one term that changes nothing — it only
 * stops the shape from being recognised, so the general path answers it. One
 * config was refused and its twin worked.
 *
 * Keying by this instead makes the fast path and the check agree with the
 * operator, at no cost: a whole number keys by its own digits with nothing in
 * front, and everything else keys by itself.
 */
/**
 * `"01"` and `"1"` share the key `"1"`; `"1.0"` and `"1"` do not share one,
 * because `==` between two texts does not read a decimal point either.
 */
export declare function matchKey(value: string): string;
//# sourceMappingURL=match-key.d.ts.map