Callable<A, B> does not exist, so a function type cannot be bounded by an aspect

GAP-FUNCTIONS-002

Callable<A, B> is not defined in std::core, so a function or closure type cannot satisfy an aspect bound and dyn Callable is unavailable.

Lifecycle

planned

Owner

language

Scope

reference/spec/functions.md#first-class-functions

Origin

metel-core#1235 records pass over the limit-phrasing lint of reference/spec/declarations.md

Affects · linked records

RFC-0161rfc

gapKnown gaps ↗

Gap

A plain function and a closure share one type, |A| -> B; there is no fun(A) -> B pointer type. The aspect that function types are sometimes described as implementing, Callable<A, B>, is not defined in std::core, so no bound names it and dyn Callable cannot be written. RFC-0161 (1-under-review) proposes the contract.

Impact

No aspect bound can require "any callable", and dyn Callable cannot be written.

Affects

• RFC-0161

Resolution

Planned, tracked as metel-core#923 (RFC-0161, 1-under-review). Deliberately kept off the ownership-and-freeze themes of the roadmap: Callable/dyn Callable completes the closure/aspect surface but establishes no new identity for the language, unlike the ownership and row-polymorphism work those themes carry. It sits with the other design settlement deferred the same way (comptime, derive, record conversions).