diff options
| author | Chayim Refael Friedman <chayimfr@gmail.com> | 2025-02-04 19:10:04 +0200 |
|---|---|---|
| committer | Chayim Refael Friedman <chayimfr@gmail.com> | 2025-02-04 19:10:04 +0200 |
| commit | 9d81503252ccae45e19888e6f7c1e2a9dee8d0ee (patch) | |
| tree | 3716e36adc84b34fbadae547678a76ec1a8ac5d1 /tests/rustdoc-ui/coverage/enum-tuple.rs | |
| parent | 54670912dad92dcb7cc8fbc91f4ce1c3fc4cb49d (diff) | |
| download | rust-9d81503252ccae45e19888e6f7c1e2a9dee8d0ee.tar.gz rust-9d81503252ccae45e19888e6f7c1e2a9dee8d0ee.zip | |
Fix a failing test
The reason this test passed previously is not because it was working as intended, but because prior to the previous commit we did not resolve the `use` at all! Now, `use self as _` is invalid code anyway (it prints E0429), and because we fallback to the value namespace if we can't resolve in the type namespace (which is a reasonable behavior), this test now actually fails. I don't think we want to change the fallback, so I removed `use self as _` and instead added a new test, where the value can be resolved in the type namespace.
Diffstat (limited to 'tests/rustdoc-ui/coverage/enum-tuple.rs')
0 files changed, 0 insertions, 0 deletions
