/**
 * Why two declarations claim one address, said to the author who has to repair
 * it.
 *
 * D115 P4 R4a. Composition is what makes these sentences hard: the conflicting
 * route or fallback may be in a file the author never opened, so every message
 * that can name an origin does, and the three causes of one collision each name
 * a different repair.
 */
import { type ComposedFallback, type ComposedRoute } from "../contracts.ts";
export declare function describeComposedRoute(entry: ComposedRoute): string;
/**
 * Why two routes claim one method and shape. Three causes reach this point and each names a
 * different repair, so the message has to tell them apart: one server composed in along two paths
 * declares its route once and cannot be narrowed at all, two routes spelling the same path have no
 * parameter names to blame, and only the third is the shape collision parameter names hide.
 */
export declare function describeRouteCollision(previous: ComposedRoute, entry: ComposedRoute): string;
/**
 * Both sides of a duplicate @notFound. A fallback a spread composes in is invisible in the author's
 * own file, so naming one contributor and not the other leaves him looking for a declaration that
 * is not there; two spreads each composing one name neither by default.
 */
export declare function describeFallbackCollision(previous: ComposedFallback, entry: ComposedFallback): string;
//# sourceMappingURL=collisions.d.ts.map