diff options
| author | Philip Herron <herron.philip@googlemail.com> | 2023-01-27 15:38:58 +0000 |
|---|---|---|
| committer | Arthur Cohen <arthur.cohen@embecosm.com> | 2023-04-06 10:47:21 +0200 |
| commit | e42c28bcfdde1f81c4908c08ee5e2da6e1c4bd93 (patch) | |
| tree | 4f616921772fa93cf14b7d0dba12b9a272772821 /gcc/rust/resolve | |
| parent | 31f1e59962b81408e37ac4f46f6b39456ee54b21 (diff) | |
| download | gcc-e42c28bcfdde1f81c4908c08ee5e2da6e1c4bd93.zip gcc-e42c28bcfdde1f81c4908c08ee5e2da6e1c4bd93.tar.gz gcc-e42c28bcfdde1f81c4908c08ee5e2da6e1c4bd93.tar.bz2 | |
gccrs: Remove monomorphization hack to setup possible associated types
During CallExpr argument type checking we may be calling a default
implementation of a trait function this will require any possible
associated types to be resolved and setup. This monomoprhization call does
this but it will premtivly do extra unification of types which will throw
off type checking later on. This fix is required for my work into type
bounds checking.
Fixes #1773
Signed-off-by: Philip Herron <herron.philip@googlemail.com>
gcc/rust/ChangeLog:
* typecheck/rust-hir-trait-reference.h: change interface to return self
* typecheck/rust-hir-trait-resolve.cc: likewise
* typecheck/rust-hir-type-check-path.cc (TypeCheckExpr::resolve_segments): likewise
* typecheck/rust-tyty-call.cc (TypeCheckCallExpr::visit): remove monomorphization hack
gcc/testsuite/ChangeLog:
* rust/compile/issue-1773.rs: New test.
Diffstat (limited to 'gcc/rust/resolve')
0 files changed, 0 insertions, 0 deletions