import { Extractor } from "../types.js";
//#region src/core/extract/extractors/literal.d.ts
/**
 * z.literal(). Values with a JS source form compile to an inline `===` chain;
 * anything else — a symbol, an object — has none, so the node retains the
 * ORIGINAL schema in `__rf[]` and codegen tests membership against its own
 * `_zod.def.values` at runtime. `Array.prototype.includes` is SameValueZero,
 * exactly the comparison zod's `new Set(def.values).has(input)` performs, and
 * reporting that same array as the issue's `values` is exactly what zod reports.
 *
 * Zod's public argument type (`util.Literal`) admits none of these, but its
 * runtime accepts them and its own parse ACCEPTS the matching value — so
 * `z.literal(someSymbol)` is a schema that really works, and previously
 * compiled to `x===undefined` (see `hasSourceForm`): it rejected the very symbol
 * it was built from and accepted `undefined`.
 */
declare const extractLiteral: Extractor;
//#endregion
export { extractLiteral };
//# sourceMappingURL=literal.d.ts.map