{"ast_node_type":"import","tokens":[{"end":92,"kind":"keyword","start":0,"text":"///"}]}
    /// keys in `Resolver::effective_visibilities` are not enough for that, because multiple
    /// While walking import chains we need to track effective visibilities per-binding, and def id
    /// bindings can correspond to a single def id in imports. So we keep a separate table.