alef 0.79.5

Opinionated polyglot binding generator for Rust libraries
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79

//! Regression coverage for the element accessor a wildcard (`container[].field`) fixture path
//! expands to in the Kotlin e2e generator.
//!
//! ~keep Kotlin was reported CLEAN by a survey of one consumer corpus's generated output. It is
//! not structurally clean: its wildcard branch routed the element half through the same
//! result-anchored `FieldResolver::accessor` the six confirmed-defective backends used, against a
//! resolver its `call_field_resolver` anchors at the call's declared result type exactly as they
//! do. That corpus simply produced no `result_fields` envelope rescue for this backend. The
//! fixture below supplies one, and the assertions fail against the pre-fix generator — an
//! accident, not an immunity.
//!
//! Kotlin's renderer lowers index 0 to `.first()` rather than a visible `[0]`, so the pre-fix
//! output was `e.records().first().kind()`: the container path applied a second time against a
//! binding that is already an element, and harder to spot in review than the `[0]` spelling.

use std::collections::{HashMap, HashSet};

use super::assertions::render_assertion;
use crate::e2e::codegen::wildcard_element_fixture::{
    WILDCARD_FIELD, assert_container_accessor_appears_once, assert_element_relative, contains_assertion,
    envelope_resolver, report_resolver,
};
use crate::e2e::field_access::FieldResolver;

const CONTAINER_ACCESSOR: &str = ".records()";

fn render(resolver: &FieldResolver) -> String {
    let mut out = String::new();
    render_assertion(
        &mut out,
        &contains_assertion(WILDCARD_FIELD),
        "result",
        "SampleTest",
        resolver,
        false,
        false,
        &HashSet::new(),
        &HashSet::new(),
        &HashMap::new(),
        false,
        false,
        false,
    );
    out
}

#[test]
fn wildcard_lambda_body_is_relative_to_the_element_binding() {
    let rendered = render(&report_resolver("kotlin"));

    assert_element_relative(&rendered, "e.kind().toString()", "e.records().first()");
    assert_container_accessor_appears_once(&rendered, CONTAINER_ACCESSOR);
}

/// The container half must keep resolving against the result variable — the fix must not turn
/// into "never anchor", which would still satisfy the assertion above.
#[test]
fn wildcard_container_stays_anchored_to_the_result_variable() {
    let rendered = render(&report_resolver("kotlin"));

    assert!(
        rendered.contains("result.records().any { e ->"),
        "container half must quantify over the result variable's own field, got: {rendered}"
    );
}

/// The stronger container control: on an envelope root the container is reachable only THROUGH
/// the `result_fields` projection, so dropping the anchoring from `accessor` — rather than only
/// from the element half — renders `result.records()`, a member the envelope does not declare.
#[test]
fn wildcard_container_keeps_its_envelope_projection() {
    let rendered = render(&envelope_resolver("kotlin"));

    assert!(
        rendered.contains("result.results().first().records().any { e ->"),
        "container half must keep the result-anchored envelope projection, got: {rendered}"
    );
    assert_container_accessor_appears_once(&rendered, CONTAINER_ACCESSOR);
}