[basic.link] The notion of the linkage of a type is no longer used for

any purpose. Remove it and move its example next to the rule that
justifies it, and simplify said example.

Author: zygoloid

source/basic.tex

@@ -445,6 +445,21 @@
 \ref{class.dtor}, and \ref{class.copy.assign}).
 An inline function or variable shall be defined in every
 translation unit in which it is odr-used outside of a discarded statement.
+\begin{example}
+\begin{codeblock}
+auto f() {
+  struct A {};
+  return A{};
+}
+decltype(f()) g();
+auto x = g();
+\end{codeblock}
+A program containing this translation unit is ill-formed
+because \tcode{g} is odr-used but not defined,
+and cannot be defined in any other translation unit
+because the local class \tcode{A} cannot be named outside this
+translation unit.
+\end{example}
 
 \pnum
 \indextext{type!incomplete}%
@@ -2456,56 +2471,6 @@
 noted, a name declared at block scope\iref{basic.scope.block} has no
 linkage.
 
-\pnum
-A type is said to have linkage if and only if:
-\begin{itemize}
-\item it is a class or enumeration type that is named (or has a name for
-linkage purposes\iref{dcl.typedef}) and the name has linkage; or
-
-\item it is an unnamed class or unnamed enumeration that is a member of a class
-with linkage; or
-
-\item it is a specialization of a class template\iref{temp}\footnote{A class
-template has the linkage of the innermost enclosing class or namespace in which
-it is declared.};
-or
-
-\item it is a fundamental type\iref{basic.fundamental}; or
-
-\item it is a compound type\iref{basic.compound} other than a class or
-enumeration, compounded exclusively from types that have linkage; or
-
-\item it is a cv-qualified\iref{basic.type.qualifier} version of a
-type that has linkage.
-\end{itemize}
-\begin{note}
-In other words, a type without linkage contains a class or enumeration that
-cannot be named outside its translation unit.
-Classes with linkage may contain members
-whose types do not have linkage.
-Typedef names are ignored in the determination
-of whether a type has linkage.
-\end{note}
-
-\begin{example}
-\begin{codeblock}
-template <class T> struct B {
-  void g(T) { }
-  void h(T);
-  friend void i(B, T) { }
-};
-
-void f() {
-  struct A { int x; };  // no linkage
-  A a = { 1 };
-  B<A> ba;              // declares \tcode{B<A>::g(A)} and \tcode{B<A>::h(A)}
-  ba.g(a);              // OK
-  ba.h(a);              // error: \tcode{B<A>::h(A)} not defined; \tcode{A} cannot be named in another translation unit
-  i(ba, a);             // OK
-}
-\end{codeblock}
-\end{example}
-
 \pnum
 Two names that are the same\iref{basic} and that are declared
 in different scopes shall denote the same variable, function,

source/classes.tex

@@ -854,8 +854,7 @@
 declaration in the class definition or its definition outside of the
 class definition declares the function as \tcode{inline} or \tcode{constexpr}.
 \begin{note}
-Member functions of a class in namespace scope have the linkage of that class.
-Member functions of a local class\iref{class.local} have no linkage.
+Member functions of a class have the linkage of the name of the class.
 See~\ref{basic.link}.
 \end{note}
 
@@ -2846,7 +2845,8 @@
 
 \pnum
 \begin{note}
-Static data members of a class in namespace scope have the linkage of that class\iref{basic.link}. A local class cannot have static data members\iref{class.local}.
+Static data members of a class in namespace scope have the linkage of the name of the class\iref{basic.link}.
+A local class cannot have static data members\iref{class.local}.
 \end{note}
 
 \pnum