diff options
| author | bors[bot] <26634292+bors[bot]@users.noreply.github.com> | 2022-04-27 13:38:41 +0000 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-04-27 13:38:41 +0000 |
| commit | 9a9bb44058a8406b41bb1ab3110e08a897772bb0 (patch) | |
| tree | 99751b78d4ca97cde368351b4aa28aeb23569c84 /gcc/rust/backend/rust-compile-resolve-path.cc | |
| parent | 60f7f998a2128aeaca1d00e8329bce22491f6f5e (diff) | |
| parent | ea38a59ee8329bb7b309400a7de57d53ad7bde31 (diff) | |
| download | gcc-9a9bb44058a8406b41bb1ab3110e08a897772bb0.zip gcc-9a9bb44058a8406b41bb1ab3110e08a897772bb0.tar.gz gcc-9a9bb44058a8406b41bb1ab3110e08a897772bb0.tar.bz2 | |
Merge #1184
1184: Fix bad name resolution on path with generic segments r=philberty a=philberty
This fix breaks down into two commits the first commit fixes the issue directly
then the second one fixes the regression that was introduced in the first.
The TLDR for this patch set is that when we resolve the path here:
module::transmute
The name-resolver wronly added the specified generic arguments into the canonical
path meaning that the root segment could not be name-resolved such that during
type resolution we iterate and apply the generic arguments appropriately to the root
segment.
In fixing this it introduced a regression exposing a few more complex issues with
inference variables but for a more complete explanation about that please read the
commit message from ea38a59ee8329bb7b309400a7de57d53ad7bde31
Fixes #1173
Co-authored-by: Philip Herron <philip.herron@embecosm.com>
Diffstat (limited to 'gcc/rust/backend/rust-compile-resolve-path.cc')
0 files changed, 0 insertions, 0 deletions