PEP 696: consolidate discussion of constraint solving in "Function Defaults" section, add new "Subtyping" section (#3648)

* PEP 696: consolidate discussion of constraint solving.

Consolidates discussion of usage of defaults in constraint solving in
the "Function Defaults" section, to make it clear that this is
experimental and unspecified.

* PEP 696: Explicitly call out that defaults do not affect subtyping.

peps/pep-0696.rst

@@ -17,8 +17,7 @@ Abstract
 
 This PEP introduces the concept of type defaults for type parameters,
 including ``TypeVar``, ``ParamSpec``, and ``TypeVarTuple``,
-which act as defaults for a type parameter when one is not specified or
+which act as defaults for type parameters for which no type is specified.
-the constraint solver isn't able to solve a type parameter to anything.
 
 Default type argument support is available in some popular languages
 such as C++, TypeScript, and Rust. A survey of type parameter syntax in
@@ -182,8 +181,7 @@ or another in-scope ``TypeVarTuple`` (see `Scoping Rules`_).
 Using Another Type Parameter as ``default``
 ''''''''''''''''''''''''''''''''''''''''''''
 
-This allows for a value to be used again when the constraints solver
+This allows for a value to be used again when the type parameter to a
-fails to solve a constraint for a type, or the type parameter to a
 generic is missing but another type parameter is specified.
 
 To use another type parameter as a default the ``default`` and the
@@ -373,11 +371,18 @@ subtype of one of the constraints.
 Function Defaults
 '''''''''''''''''
 
-We leave the semantics of type parameter defaults in generic functions
+In generic functions, type checkers may use a type parameter's default when the
-unspecified, as ensuring the ``default`` is returned in every code path
+type parameter cannot be solved to anything. We leave the semantics of this
-where the type parameter can go unsolved may be too hard to implement.
+usage unspecified, as ensuring the ``default`` is returned in every code path
-Type checkers are free to either disallow this case or experiment with
+where the type parameter can go unsolved may be too hard to implement. Type
-implementing support.
+checkers are free to either disallow this case or experiment with implementing
+support.
+
+::
+
+   T = TypeVar('T', default=int)
+   def func(x: int | set[T]) -> T: ...
+   reveal_type(func(0))  # a type checker may reveal T's default of int here
 
 Defaults following ``TypeVarTuple``
 '''''''''''''''''''''''''''''''''''
@@ -413,6 +418,13 @@ for the ``ParamSpec`` and one for the ``TypeVarTuple``.
    Foo[int, str]  # Ts = (int, str), P = [float, bool]
    Foo[int, str, [bytes]]  # Ts = (int, str), P = [bytes]
 
+Subtyping
+'''''''''
+
+Type parameter defaults do not affect the subtyping rules for generic classes.
+In particular, defaults can be ignored when considering whether a class is
+compatible with a generic protocol.
+
 ``TypeVarTuple``\ s as Defaults
 '''''''''''''''''''''''''''''''