CWG2667 Named module imports do not import macros

Author: burblebee

source/modules.tex

@@ -512,6 +512,13 @@
 \end{footnote}
 These rules can in turn lead to the importation of yet more
 translation units.
+\begin{note}
+Such indirect importation does not make macros available,
+because a translation unit is
+a sequence of tokens in translation phase 7\iref{lex.phases}.
+Macros can be made available by directly importing header units
+as described in \ref{cpp.import}.
+\end{note}
 
 \pnum
 A module implementation unit shall not be exported.

source/preprocessor.tex

@@ -929,6 +929,18 @@
 int a = Y;      // OK, active macro definitions \#2 and \#4 are valid redefinitions
 int c = Z;      // error: active macro definitions \#3 and \#5 are not valid redefinitions of \tcode{Z}
 \end{codeblocktu}
+
+\begin{codeblocktu}{Module unit \tcode{f}}
+export module f;
+export import "a.h";
+
+int a = Y;      // OK
+\end{codeblocktu}
+
+\begin{codeblocktu}{Translation unit \tcode{\#1}}
+import f;
+int x = Y;      // error: \tcode{Y} is neither a defined macro nor a declared name
+\end{codeblocktu}
 \end{example}
 \indextext{macro!import|)}