diff options
| author | Michael Goulet <michael@errs.io> | 2023-05-08 09:30:23 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-05-08 09:30:23 -0700 |
| commit | bbea63f627433eb00ef9ac235bcced35e4cfbd4c (patch) | |
| tree | 5089dc897e494907635f7377f6ce905434a06d2a /tests/rustdoc-js-std/parser-errors.js | |
| parent | 24ba82de4e4acf4ea8b420fb81f0f00dde0bbcba (diff) | |
| parent | 3bbb69eaa02f5dfa6bcf23e667ec0614c64d3502 (diff) | |
| download | rust-bbea63f627433eb00ef9ac235bcced35e4cfbd4c.tar.gz | |
Rollup merge of #111354 - jonas-schievink:enable-future-combinators, r=compiler-errors
Fix miscompilation when calling default methods on `Future`
In https://github.com/rust-lang/rust/issues/111264 I discovered a lingering miscompilation when calling a default method on `Future` (none currently exist). https://github.com/rust-lang/rust/pull/111279 added a debug assertion, which sadly doesn't help much since to my knowledge stage0 is not built with them enabled, and it still doesn't make default methods work like they should.
This PR fixes `resolve_instance` to resolve default methods on `Future` correctly, allowing library contributors to add `Future` combinators without running into ICEs or miscompilations. I've tested this as part of https://github.com/rust-lang/rust/pull/111347, but no test is included here (assuming that future methods include their own tests that would cover this sufficiently).
r? `@compiler-errors`
Diffstat (limited to 'tests/rustdoc-js-std/parser-errors.js')
0 files changed, 0 insertions, 0 deletions