Skip to main content

phase_locale_bundle_ambiguity

Function phase_locale_bundle_ambiguity 

Source
pub fn phase_locale_bundle_ambiguity(
    parsed: &[ParsedFile],
    groups: &BTreeMap<String, Vec<usize>>,
    kinds: &BTreeMap<String, UnitKind>,
    unit_uses: &HashMap<String, Vec<String>>,
    unit_flattened: &HashMap<String, HashMap<String, String>>,
    errors: &mut ErrorSink,
)
Expand description

Locale capability track, slice 2 (#882): a context whose direct uses reaches two or more message-bundle commons has no principled single answer for what Locale.current() should negotiate against — but this is only worth diagnosing when the context actually consumes bynk { Locale } at all; a context with 2+ bundles that never touches Locale has nothing ambiguous to resolve.

P5.0 (design/tracks/semantics-in-the-checker.md §6): relocated verbatim from bynk-emit/src/project/validate.rs’s check_locale_bundle_ambiguity — category 3 of analysis.rs’s own seven-category accounting, the second of this slice’s two live editor-diagnostics regressions.