diff options
| author | Philip Herron <philip.herron@embecosm.com> | 2021-10-15 18:02:51 +0100 |
|---|---|---|
| committer | Philip Herron <philip.herron@embecosm.com> | 2021-10-22 10:34:31 +0100 |
| commit | d755769bd15209193d1c178862ed3e01ba5c3d9d (patch) | |
| tree | de4344d1cd0cfc3204cd0816fdf2678c02a52896 /gcc/rust/rustspec.cc | |
| parent | a80bcfc5b1cb471d904ae9135256d9d0b0d77cd4 (diff) | |
| download | gcc-d755769bd15209193d1c178862ed3e01ba5c3d9d.zip gcc-d755769bd15209193d1c178862ed3e01ba5c3d9d.tar.gz gcc-d755769bd15209193d1c178862ed3e01ba5c3d9d.tar.bz2 | |
BugFix: TypePath resolution to handle associated types
TypePath's can be fully resolved at name resolution time for example a
primitive types are single segments which can be resolved. But in the event
of a generic TypeBound path such as: T::A where T is the generic type param
in a function and A is its own associated type this require's the
resolution to be split over the name resolver and type resolver.
Like PathInExpression's the name resolver is able to resolve the root
segment of 'T' but requires a path probe on the type-bounds of T to find
the associated type 'A'.
Fixes #746
Diffstat (limited to 'gcc/rust/rustspec.cc')
0 files changed, 0 insertions, 0 deletions