diff options
| author | 许杰友 Jieyou Xu (Joe) <39484203+jieyouxu@users.noreply.github.com> | 2024-05-18 20:38:04 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-05-18 20:38:04 +0100 |
| commit | f08746a95de58004d0ab42bdf252456883bc5c1a (patch) | |
| tree | 41427b9b6f56afbf47c22e58814b870bef673dc7 /compiler/rustc_codegen_gcc/example/std_example.rs | |
| parent | c00957a3e269219413041a4e3565f33b1f9d0779 (diff) | |
| parent | fa829feb2f7a3fee5890f3acf57b66029b123d18 (diff) | |
| download | rust-f08746a95de58004d0ab42bdf252456883bc5c1a.tar.gz rust-f08746a95de58004d0ab42bdf252456883bc5c1a.zip | |
Rollup merge of #125214 - compiler-errors:gat-guide, r=lcnr
Only make GAT ambiguous in `match_projection_projections` considering shallow resolvability In #123537, I tweaked the hack from #93892 to use `resolve_vars_if_possible` instead of `shallow_resolve`. This considers more inference guidance ambiguous. This resulted in crater regressions in #125196. I've effectively reverted the change to the old behavior. That being said, I don't *like* this behavior, but I'd rather keep it for now since #123537 was not meant to make any behavioral changes. See the attached example. This also affects the new solver, for the record, which doesn't have any rules about not guiding inference from param-env candidates which may constrain GAT args as a side-effect. r? `@lcnr` or `@jackh726`
Diffstat (limited to 'compiler/rustc_codegen_gcc/example/std_example.rs')
0 files changed, 0 insertions, 0 deletions