diff options
| author | Corey Farwell <coreyf@rwell.org> | 2017-03-22 23:37:59 -0400 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2017-03-22 23:37:59 -0400 |
| commit | cc98dfc8d265a40c6e1463022b862ede01f4ed26 (patch) | |
| tree | 220e5c46fa60e35de9d2f3154c3a37243b4e6d15 /src/test | |
| parent | 916c0b83ccabea3be0ee7b4861c56a9ef44b6804 (diff) | |
| parent | 090767b5ef59188e5defb466ff6580b99891f1ed (diff) | |
| download | rust-cc98dfc8d265a40c6e1463022b862ede01f4ed26.tar.gz rust-cc98dfc8d265a40c6e1463022b862ede01f4ed26.zip | |
Rollup merge of #40518 - michaelwoerister:hir-id, r=eddyb
Introduce HirId, a replacement for ast::NodeId after lowering to HIR This is the first step towards implementing #40303. This PR introduces the `HirId` type and generates a `HirId` for everything that would be assigned one (i.e. stuff in the HIR), but the HIR data types still use `NodeId` for now. Changing that is a big refactoring that I want to do in a separate PR. A `HirId` uniquely identifies a node in the HIR of the current crate. It is composed of the `owner`, which is the `DefIndex` of the directly enclosing `hir::Item`, `hir::TraitItem`, or `hir::ImplItem` (i.e. the closest "item-like"), and the `local_id` which is unique within the given owner. This PR is also running a number of consistency checks for the generated `HirId`s: - Does `NodeId` in the HIR have a corresponding `HirId`? - Is the `owner` part of each `HirId` consistent with its position in the HIR? - Do the numerical values of the `local_id` part all lie within a dense range of integers? cc @rust-lang/compiler r? @eddyb or @nikomatsakis
Diffstat (limited to 'src/test')
| -rw-r--r-- | src/test/compile-fail/region-bounds-on-objects-and-type-parameters.rs | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/test/compile-fail/region-bounds-on-objects-and-type-parameters.rs b/src/test/compile-fail/region-bounds-on-objects-and-type-parameters.rs index 503b577b1f1..fd8d5ff9e7e 100644 --- a/src/test/compile-fail/region-bounds-on-objects-and-type-parameters.rs +++ b/src/test/compile-fail/region-bounds-on-objects-and-type-parameters.rs @@ -18,7 +18,7 @@ trait SomeTrait { } // Bounds on object types: -struct Foo<'a,'b,'c> { //~ ERROR parameter `'b` is never used +struct Foo<'a,'b,'c> { //~ ERROR parameter `'c` is never used // All of these are ok, because we can derive exactly one bound: a: Box<IsStatic>, b: Box<Is<'static>>, |