meta.language.classes.abstract_complete

A concrete class must implement every inherited abstract method.

Read in specification context · design/meta/language.md

Tests and review

Indexed tests and the implementation-completeness and test-adequacy review; no test run is implied.

Implemented sage_meta::rejects_cycles_and_incomplete_concrete_classes

crates/sage-meta/tests/language.rs · test:language

#![allow(unused)]
fn main() {
#[test]
#[sage::test(meta.language.classes.abstract_complete)]
fn rejects_cycles_and_incomplete_concrete_classes() {
    let errors = check(
        r#"
        abstract class Base { """Base.""" fn run() -> crate::Value { """Run.""" abstract; } }
        class Concrete extends crate::Base { """Missing implementation.""" }
        class A extends crate::B { """Cycle.""" }
        class B extends crate::A { """Cycle.""" }
    "#,
    );
    assert!(
        errors
            .iter()
            .any(|e| e.message.contains("does not implement"))
    );
    assert!(
        errors
            .iter()
            .any(|e| e.message.contains("inheritance cycle"))
    );
}
}

See more source ↗

Review: Accepted · Codex /root/anchor_189.

Source review: the complete claim requires every inherited abstract method to have an implementation in a concrete class. The sole ordinary implementation association is Model::check in validate.rs. Its non-Abstract guard exempts abstract classes; nested ancestor/method iteration covers all inherited declarations, including distant ancestors. method selects the nearest declaration using the cycle-bounded ancestors traversal, so a concrete override or inherited concrete implementation satisfies the obligation, while a selected declaration with no envelope emits the concrete-class-does-not-implement diagnostic. All these helpers are in the captured implementation file. The sole ordinary associated test, rejects_cycles_and_incomplete_concrete_classes, visibly constructs Base.run as abstract and Concrete without an override, then asserts a does-not-implement diagnostic. Removing completeness checking would fail that assertion; its separate cyclic classes and inheritance-cycle assertion also exercise safe traversal. The captured check helper parses the supplied model and passes it directly to validate. This meaningful negative case, together with inspection of exhaustive traversal and nearest-method selection, supports the complete claim. There are no TODO/N/A entries or deferred prerequisites. Baseline: independently verified exact byte equality of both current validate.rs and language.rs with historical source snapshots; reassessed the supplied prior rationale against current claim, full association set, implementation and test assertions. Execution: ran review start/read and byte comparisons; no behavioral tests or build were run by this reviewer. The coordinator separately reports 321 functional tests and cargo build passing; that is not personal execution evidence. No edits requested.

Browse meta anchors

116 anchors

Anchor Implementation Tests

meta (116) 102 Implemented24 TODO 103 Implemented36 TODO

meta.anchors (22) 22 Implemented 21 Implemented12 TODO

anchor_pages Implemented ImplementedTODO

Every specification anchor has a stable page identifying the rule and showing its definition, context, implementation entries, and tests/evidence. The page includes Rust excerpts and access to surrounding source, and exposes each entry’s placeholder status and explanation. Multiple sites remain individually inspectable rather than being reduced to a single coverage badge.

Symposiun AGentic Environment (SAGE)

meta.language.classes.abstract_complete

Implementation

Tests and review