Response to comments

Author: ilevkivskyi

Doc/library/dis.rst

@@ -723,47 +723,6 @@ All of the following opcodes use their arguments.
    are put onto the stack right-to-left.
 
 
-.. opcode:: BUILD_TUPLE_UNPACK (count)
-
-   Pops ``count`` iterables from the stack, joins them in a single tuple,
-   and pushes the result.
-
-   .. versionadded:: 3.5
-
-
-.. opcode:: BUILD_LIST_UNPACK (count)
-
-   This is similar to :opcode:`BUILD_TUPLE_UNPACK`, but pushes a list
-   instead of tuple.
-
-   .. versionadded:: 3.5
-
-
-.. opcode:: BUILD_SET_UNPACK (count)
-
-   This is similar to :opcode:`BUILD_TUPLE_UNPACK`, but pushes a set
-   instead of tuple.
-
-   .. versionadded:: 3.5
-
-
-.. opcode:: BUILD_MAP_UNPACK (count)
-
-   Pops ``count`` mappings from the stack, joins them in a single dictionary,
-   and pushes the result.
-
-   .. versionadded:: 3.5
-
-
-.. opcode:: BUILD_MAP_UNPACK_WITH_CALL (count)
-
-   This is similar to :opcode:`BUILD_MAP_UNPACK`,
-   but is used for ``f(**x, **y, **z)`` call syntax. The stack item at position
-   ``count + 2`` should be the corresponding callable ``f``.
-
-   .. versionadded:: 3.5
-
-
 .. opcode:: STORE_ATTR (namei)
 
    Implements ``TOS.name = TOS1``, where *namei* is the index of name in
@@ -813,11 +772,13 @@ All of the following opcodes use their arguments.
 
 .. opcode:: BUILD_MAP (count)
 
-   Pushes a new dictionary object onto the stack. Pops ``2 * count`` items
+   Pushes a new dictionary object onto the stack.  Pops ``2 * count`` items
    so that the dictionary holds ``count`` entries:
    ``{..., TOS3: TOS2, TOS1: TOS}``.
 
    .. versionchanged:: 3.5
+      The dictionary is created from stack items instead of creating an
+      empty dictionary pre-sized to hold ``count`` items.
 
 
 .. opcode:: BUILD_CONST_KEY_MAP (count)
@@ -837,6 +798,49 @@ All of the following opcodes use their arguments.
    .. versionadded:: 3.6
 
 
+.. opcode:: BUILD_TUPLE_UNPACK (count)
+
+   Pops ``count`` iterables from the stack, joins them in a single tuple,
+   and pushes the result. This bytecode is used for implementing iterable
+   unpacking in tuple displays ``(*x, *y, *z)``.
+
+   .. versionadded:: 3.5
+
+
+.. opcode:: BUILD_LIST_UNPACK (count)
+
+   This is similar to :opcode:`BUILD_TUPLE_UNPACK`, but pushes a list
+   instead of tuple.
+
+   .. versionadded:: 3.5
+
+
+.. opcode:: BUILD_SET_UNPACK (count)
+
+   This is similar to :opcode:`BUILD_TUPLE_UNPACK`, but pushes a set
+   instead of tuple.
+
+   .. versionadded:: 3.5
+
+
+.. opcode:: BUILD_MAP_UNPACK (count)
+
+   Pops ``count`` mappings from the stack, joins them in a single dictionary,
+   and pushes the result.
+
+   .. versionadded:: 3.5
+
+
+.. opcode:: BUILD_MAP_UNPACK_WITH_CALL (oparg)
+
+   This is similar to :opcode:`BUILD_MAP_UNPACK`,
+   but is used for ``f(**x, **y, **z)`` call syntax. The lowest byte of
+   ``oparg`` is the count of mappings, the relative position of the
+   corresponding callable ``f`` is encoded in the second byte of ``oparg``.
+
+   .. versionadded:: 3.5
+
+
 .. opcode:: LOAD_ATTR (namei)
 
    Replaces TOS with ``getattr(TOS, co_names[namei])``.