diff options
| author | bors <bors@rust-lang.org> | 2018-05-28 19:16:27 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2018-05-28 19:16:27 +0000 |
| commit | 5bf68db6ecda0dd4788311a41b5c763d35597c96 (patch) | |
| tree | 339edc1aa1989cc9f311504c7d4fef82760e4d78 /src/rustllvm/RustWrapper.cpp | |
| parent | 2612bbcba08dd81730edd8f2139005fb7a409294 (diff) | |
| parent | 1b7488d40b6182e1104c2472fd80d4333e2f2861 (diff) | |
| download | rust-5bf68db6ecda0dd4788311a41b5c763d35597c96.tar.gz rust-5bf68db6ecda0dd4788311a41b5c763d35597c96.zip | |
Auto merge of #50929 - zackmdavis:hiridification_initiative, r=michaelwoerister
operate on `HirId` instead of `NodeId` in `hir::Pat::each_binding`, and consequences of that See #50928 for motivation. Questions— * Is #50928 actually a good idea as a plan of record, or is there some reason to keep `NodeId`s? * Are the uses of `find_node_for_hir_id` in this initial submission OK (see the FIXME comments)? * Can we bikeshed a better method names `struct_span_lint_hir` _&c._? (Coined in analogy to the `struct_span_lint_node` and `NodeId`, but it feels kind of semantically clunky.) r? @michaelwoerister
Diffstat (limited to 'src/rustllvm/RustWrapper.cpp')
0 files changed, 0 insertions, 0 deletions