0a088ead85
Fix a few bugs where we would fail to properly determine header to module correspondence when determining whether to suggest a #include or import, and suggest a #include more often in language modes where there is no import syntax. Generally, if the target is in a header with include guards or #pragma once, we should suggest either #including or importing that header, and not importing a module that happens to textually include it. In passing, improve the notes we attach to the corresponding diagnostics: calling an entity that we couldn't see "previous" is confusing.
13 lines
516 B
C++
13 lines
516 B
C++
// RUN: rm -rf %t
|
|
// RUN: %clang_cc1 -triple x86_64-windows-msvc -fms-extensions -fms-compatibility -x c++ -std=c++20 -fmodules-cache-path=%t -fmodules -fimplicit-module-maps -I %S/Inputs/ms-enums %s -verify -fno-modules-error-recovery
|
|
|
|
#include "B.h"
|
|
// expected-note@A.h:1 {{declaration here is not visible}}
|
|
// expected-note@A.h:1 2{{definition here is not reachable}}
|
|
|
|
fwd_enum gv_enum; // expected-error {{must be imported}}
|
|
|
|
struct Foo {
|
|
enum fwd_enum enum_field; // expected-error 2 {{must be imported}}
|
|
};
|