diff options
| author | bors[bot] <26634292+bors[bot]@users.noreply.github.com> | 2022-07-08 11:47:17 +0000 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-07-08 11:47:17 +0000 |
| commit | e1293ae35777427e1c87659ae21f9bca5f6395d6 (patch) | |
| tree | 362332a85d7d4e27ed53f91a2f8293817fafc856 /gcc/rust/resolve/rust-ast-resolve-expr.cc | |
| parent | 33eb5c938ac41ff5e65c3a8d947d033b32d31ace (diff) | |
| parent | fb27d1452b31d5485b1fce692f14279472cf0baf (diff) | |
| download | gcc-e1293ae35777427e1c87659ae21f9bca5f6395d6.zip gcc-e1293ae35777427e1c87659ae21f9bca5f6395d6.tar.gz gcc-e1293ae35777427e1c87659ae21f9bca5f6395d6.tar.bz2 | |
Merge #1366
1366: Refactor mappings class and HIR lowering to be consistent r=philberty a=philberty
In order to support loading extern crates and use statements we needed to
clarify the usage of NodeId and HirId within gccrs. Each of these id's were
nested behind the CrateNum but the type resolution, linting and code-gen
passes do not support that level of nesting.
In order to get metadata exports and imports working lets focus on gccrs
supporting compilation of a single crate at a time. This means the crate
prefix only matters for imports and limits the complexity here. Down the
line there might be a way to leverage DefId's for all Path resolution
which could solve this problem but significant refactoring would be
required here to do this properly and its not nessecary for a basic working
rust compiler.
The mappings changes here will help us resolve issues like #1361 much more
easily.
Co-authored-by: Philip Herron <philip.herron@embecosm.com>
Diffstat (limited to 'gcc/rust/resolve/rust-ast-resolve-expr.cc')
0 files changed, 0 insertions, 0 deletions