HIR (previously known as descriptors) provides a high-level object oriented access to Rust code.
The principal difference between HIR and syntax trees is that HIR is bound to a particular crate instance. That is, it has cfg flags and features applied. So, the relation between syntax and HIR is many-to-one.
HIR is the public API of the all of the compiler logic above syntax trees. It is written in “OO” style. Each type is self contained (as in, it knows it’s parents and full context). It should be “clean code”.
hir_* crates are the implementation of the compiler logic.
They are written in “ECS” style, with relatively little abstractions.
Many types are not self-contained, and explicitly use local indexes, arenas, etc.
hir is what insulates the “we don’t know how to actually write an incremental compiler”
from the ide with completions, hovers, etc. It is a (soft, internal) boundary:
Re-exports various subcrates databases so that the calling code can depend
Re-export diagnostics such that clients of
A map of all publicly exported items in a crate.
Configuration options used for conditional compilation on items with
hir::Crate describes a single crate. It’s the main interface with which a crate’s dependencies interact. Mostly, it should be just a proxy for the root module.
Input to the analyzer is a set of files, where each file is identified by
Primary API to get semantic information, like types, from syntax trees.
A Data Type
A simple configuration value passed in from the outside.
The defs which have a body.
The defs which can be visible in the module.
For IDE only
Visibility of an item, with the path resolved.