Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Completed proposals

These proposals have shipped within their agreed scope, or completed the experiment or investigation identified in their entry. They preserve design rationale and alternatives; the reference and tutorial describe current behavior. Further extensions listed below do not make the completed scope pending again. The backlog remains the only work queue.

See the proposal index for partially implemented and unimplemented designs and the policy for moving completed proposals.

ProposalReferenceFurther work
Boxed protocol objectsProtocol objectsFurther protocol capabilities remain separate from the delivered erased-owner contract
Positive and NonNegative integer domain typesNumbers, std conventionsB96 Bounded; issue #686
Single-file scriptsScript runnerB17/B18: wider executable-cache coverage
Library-owned operations and backend hooks — investigation complete; no language changeProtocols, visibilityB29; future default/final methods and private-hook grants belong to Protocol method bodies
Fluent iterator pipelinesPipelinesB75 extensions; related B12, B22, B24
Owned response experimentField movesB72: real HTTP integration remains unexplored
Flat class layoutValue representations, memoryB19 performance extensions; related B35
Runtime allocation auditAllocation and trapsB13
References, ownership, and explicit copyingOwnershipB11
One immutable str with explicit lengthsTextB12, B27
Sum types and enumsEnums, matchingB19, B33
Generics, structural protocols, context managers, and error propagationGenerics, resource scopesB11, B14, B29
Native owned generatorsGeneratorsUnscheduled
Allocation-free generator frames and rangesGenerators, rangesB12
Callable surface reviewFunctionsB32
Stored closure environmentsConsuming and stored closuresB11, B32
Native concurrency contractConcurrencyB13, B24, B28
Bounded channel implementationChannelsDeferred B22 extensions
Named arguments and fresh defaultsSignatures and callsB36 refinements; unpacking remains separate
Human-readable formatting and error reportsstd.report, entry reportsB71 extensions; Failure remains a deliberate last resort
Explicit error composition, with experiment and production evidencestd.error, std.io.typed, std.http.typed, HTTP clientB71 additive extensions and deferred benchmark-template migration
Finite error sets as anonymous sumsAnonymous sums, propagationB14/B71: guards, residual-set inference and empty sums
Bundled HTTP acceptanceHTTP qualification, client, serverPreserve B66 gates; additional platforms and HTTP/2 or HTTP/3 are separate scope
Explicit applications, modules, and executable lessonsEntry point, modules, runnable documentationB17: re-exports and module caching; literate lesson sources not adopted
Plenty’s next language phase, a design reviewPer topic in its outcome tableB13, B23, and the extensions it lists
Python slice syntax, with its implementation planSlicesB39: borrowed views &xs[a:b] (issue #581); issue #583
Checked arithmetic blocksNumbersChecked shifts and casts unscheduled; class patterns landed with issue #558
Rust compiler boundaries and measured performance — steps 1–6 and legacy-syntax removalFrontend, cacheB17 compilation session; B19 module replay and frontend candidates