gh-96408: Document difference between set-like view and sets.

While using set operators, set-like views accept any iterable as the
other operand, unlike sets which only accept sets as the input.

Co-authored-by: Filip Łajszczak <filip@lajszczak.dev>

Author: caseneuve

Doc/library/stdtypes.rst

@@ -4692,15 +4692,19 @@ support membership tests:
 Keys views are set-like since their entries are unique and hashable.  If all
 values are hashable, so that ``(key, value)`` pairs are unique and hashable,
 then the items view is also set-like.  (Values views are not treated as set-like
-since the entries are generally not unique.)  For set-like views, all of the
-operations defined for the abstract base class :class:`collections.abc.Set` are
-available (for example, ``==``, ``<``, or ``^``).
+since the entries are generally not unique.)
+
+For set-like views, all of the operations defined for the abstract base class
+:class:`collections.abc.Set` are available (for example, ``==``, ``<``, or
+``^``).  The difference between sets and set-like views is that unlike sets,
+dictionary views accept any iterable as the other operand.
 
 An example of dictionary view usage::
 
    >>> dishes = {'eggs': 2, 'sausage': 1, 'bacon': 1, 'spam': 500}
    >>> keys = dishes.keys()
    >>> values = dishes.values()
+   >>> items = dishes.items()
 
    >>> # iteration
    >>> n = 0
@@ -4727,6 +4731,12 @@ An example of dictionary view usage::
    >>> keys ^ {'sausage', 'juice'}
    {'juice', 'sausage', 'bacon', 'spam'}
 
+   >>> # set operations against iterables
+   >>> keys | ['juice', 'juice', 'juice']
+   {'juice', 'sausage', 'bacon', 'spam', 'eggs'}
+   >>> items ^ (('sausage', 1), ('juice', 3))
+   {('bacon', 1), ('eggs', 2), ('juice', 3), ('spam', 500)}
+
    >>> # get back a read-only proxy for the original dictionary
    >>> values.mapping
    mappingproxy({'eggs': 2, 'sausage': 1, 'bacon': 1, 'spam': 500})