diff options
| author | Philip Herron <philip.herron@embecosm.com> | 2022-05-24 15:43:53 +0100 |
|---|---|---|
| committer | Philip Herron <philip.herron@embecosm.com> | 2022-05-25 11:54:00 +0100 |
| commit | d01ae2ab56be6b515a863184baad496c50363fe6 (patch) | |
| tree | 851d3e1db5b2a050e364439ab5aaf0ca153d1d88 /gcc/rust/backend/rust-compile-pattern.cc | |
| parent | d09b135116f2bd56fbab054a9a0122cc6b59e06e (diff) | |
| download | gcc-d01ae2ab56be6b515a863184baad496c50363fe6.zip gcc-d01ae2ab56be6b515a863184baad496c50363fe6.tar.gz gcc-d01ae2ab56be6b515a863184baad496c50363fe6.tar.bz2 | |
Remove old hack to handle type inferencing in untyped decalred bindings
In the case where you define let a; with no type to then use this binding
and let type inferencing infer the type we used this code to implicitly
generate a new type binding to the resolved node id of the the lvalue.
This was very dangerous and was always meant to be a stop gap untill we
supported more of type inferencing. The issue here was that we were badly
overriting a function types within the type-context which hits an ICE
in the method resolution code which is expecting function TyTy's within
in order to match methods correctly.
Fixes #1274 #1273
Diffstat (limited to 'gcc/rust/backend/rust-compile-pattern.cc')
0 files changed, 0 insertions, 0 deletions