You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
### How queries interact with external crate metadata
178
+
179
+
When a query is made for an external crate (i.e., a dependency), the query system needs to load the information from that crate's metadata.
180
+
This is handled by the [`rustc_metadata` crate][rustc_metadata], which is responsible for decoding and providing the information stored in the `.rmeta` files.
181
+
182
+
The process works like this:
183
+
184
+
1. When a query is made, the query system first checks if the `DefId` refers to a local or external crate by checking if `def_id.krate == LOCAL_CRATE`.
185
+
This determines whether to use the local provider from [`Providers`][providers_struct] or the external provider from [`ExternProviders`][extern_providers_struct].
186
+
187
+
2. For external crates, the query system will look for a provider in the [`ExternProviders`][extern_providers_struct] struct.
188
+
The `rustc_metadata` crate registers these external providers through the `provide_extern` function in `rustc_metadata/src/rmeta/decoder/cstore_impl.rs`. Just like:
let cdata = CStore::from_tcx(tcx).get_crate_data(def_id.krate);
195
+
cdata.foo(def_id.index)
196
+
};
197
+
// Register other external providers...
198
+
}
199
+
```
200
+
201
+
1. The metadata is stored in a binary format in `.rmeta` files that contains pre-computed information about the external crate, such as types, function signatures, trait implementations, and other information needed by the compiler. When an external query is made, the `rustc_metadata` crate:
202
+
- Loads the `.rmeta` file for the external crate
203
+
- Decodes the metadata using the `Decodable` trait
204
+
- Returns the decoded information to the query system
205
+
206
+
This approach avoids recompiling external crates, allows for faster compilation of dependent crates, and enables incremental compilation to work across crate boundaries.
207
+
208
+
Here is a simplified example, when you call `tcx.type_of(def_id)` for a type defined in an external crate, the query system will:
209
+
1. Detect that the `def_id` refers to an external crate by checking `def_id.krate != LOCAL_CRATE`
210
+
2. Call the appropriate provider from `ExternProviders` which was registered by `rustc_metadata`
211
+
3. The provider will load and decode the type information from the external crate's metadata
212
+
4. Return the decoded type to the caller
213
+
214
+
This is why most `rustc_*` crates only need to provide local providers - the external providers are handled by the metadata system.
215
+
The only exception is when a crate needs to provide special handling for external queries, in which case it would implement both local and external providers.
0 commit comments