Method file_context

src/util.rs:1569–1607

Gather the per-file context (classes, use-map, namespace) in one call. This replaces the repeated lock-and-unwrap boilerplate that was duplicated across the completion handler, definition resolver, member definition, implementation resolver, and variable definition modules. Each of those sites used to have three nearly-identical blocks acquiring `uri_classes_index`, `use_map`, and `namespace_map

(&self, uri: &str)

    /// blocks acquiring `uri_classes_index`, `use_map`, and `namespace_map` locks
    /// and extracting the entry for a given URI.
    pub(crate) fn file_context(&self, uri: &str) -> FileContext {
        let classes = self
            .uri_classes_index
            .read()
            .get(uri)
            .cloned()
            .unwrap_or_default();

        // The legacy use_map (short name → FQN from `use` statements)
        // remains the canonical import table.  `resolved_names` is a
        // supplementary data source for consumers that can query by
        // byte offset — it must NOT replace the use_map because
        // `to_use_map()` only contains names that are actually
        // *referenced* in the code, not all *declared* imports.
        // The unused-imports diagnostic relies on seeing declared-but-
        // unreferenced imports.
        let use_map = self
            .file_imports
            .read()
            .get(uri)
            .cloned()
            .unwrap_or_default();

        let namespace = self
            .file_namespaces
            .read()
            .get(uri)
            .and_then(|spans| spans.first())
            .and_then(|s| s.namespace.clone());

        let resolved_names = self.resolved_names.read().get(uri).cloned();

        FileContext {
            classes,
            use_map,
            namespace,
            resolved_names,
        }
    }

    /// Like [`file_context`](Self::file_context) but resolves the namespace
    /// for the namespace block that contains `byte_offset`.