assertThat(dispatcher.runningCalls())
      .containsExactlyInAnyOrder(a1, a2)
    assertThat(dispatcher.queuedCalls()).isEmpty()

    // Cancel some calls. That doesn't impact running or queued.
    a2.cancel()
    a3.cancel()
    assertThat(dispatcher.runningCalls())
      .containsExactlyInAnyOrder(a1, a2)
    assertThat(dispatcher.queuedCalls()).isEmpty()

==== Use randomized-testing for coverage

In general, randomization should be used for parameters that are not expected
to affect the behavior of the functionality that is being tested. For instance
the number of shards should not impact `date_histogram` aggregations, and the
choice of the `store` type (`niofs` vs `mmapfs`) does not affect the results of
a query. Such randomization helps improve confidence that we are not relying on

	ZCNOT Z7.D, P4.Z, Z13.D                           // edb0cb04
	ZCNT Z7.D, P4.M, Z13.D                            // edb0da04
	ZCNT Z7.D, P4.Z, Z13.D                            // edb0ca04
	ZCOMPACT Z7.D, P4, Z13.D                          // ed90e105
	ZCOMPACT Z7.D, P4, Z13.D                          // ed90e105
	ZDECP P14.S, Z26.S                                // da81ad25
	ZEOR Z15.B, Z0.B, P3.M, Z0.B                      // e00d1904

  @Override
  public boolean containsKey(@Nullable Object key) {
    // does not impact recency ordering
    if (key == null) {
      return false;
    }
    int hash = hash(key);
    return segmentFor(hash).containsKey(key, hash);
  }

  @Override
  public boolean containsValue(@Nullable Object value) {
    // does not impact recency ordering
    if (value == null) {
      return false;
    }

   * previously configured separator between each.
   */
  public String join(Iterable<?> parts) {
    // We don't use the same optimization here as in the JRE flavor.
    // TODO: b/381289911 - Evaluate the performance impact of doing so.
    return join(parts.iterator());
  }

  /*
   * TODO: b/381289911 - Make the Iterator overload use StringJoiner (including Android or not)—or

 *  Breaking: Change `RecordedRequest.body` from a mutable `Buffer` to an immutable `ByteString`.

 *  Breaking: Adopt Okio's new `Socket` interface for `MockResponse.socketHandler`.

Note that any _Breaking_ changes above impact only APIs introduced in earlier 5.0.0-alpha releasees.
We don't break binary compatibility with non-alpha APIs.


## Version 5.0.0-alpha.16

_2025-05-29_

	ZCNT Z1.S, P13.Z, Z11.B                           // ERROR "illegal combination from SVE"
	ZCNT Z1.S, P13.Z, Z11.B                           // ERROR "illegal combination from SVE"
	ZCOMPACT Z1.S, P13.Z, Z11.B                       // ERROR "illegal combination from SVE"
	ZCOMPACT Z1.S, P13.Z, Z11.B                       // ERROR "illegal combination from SVE"
	ZDECP P14.B, Z7.D                                 // ERROR "illegal combination from SVE"

pkg encoding/hex, func EncodedLen(int) int
pkg encoding/hex, method (InvalidByteError) Error() string
pkg encoding/hex, type InvalidByteError uint8
pkg encoding/hex, var ErrLength error
pkg encoding/json, func Compact(*bytes.Buffer, []uint8) error
pkg encoding/json, func HTMLEscape(*bytes.Buffer, []uint8)
pkg encoding/json, func Indent(*bytes.Buffer, []uint8, string, string) error
pkg encoding/json, func Marshal(interface{}) ([]uint8, error)

    responses. Both types of calls can be canceled via the `Call` or the
    `OkHttpClient`.

 *  **URLConnection support has moved to the okhttp-urlconnection module.**
    If you're upgrading from 1.x, this change will impact you. You will need to
    add the `okhttp-urlconnection` module to your project and use the
    `OkUrlFactory` to create new instances of `HttpURLConnection`:

    ```java
    // OkHttp 1.x:

Ein großartiges Tool, sehr unterbewertet. Es sollte weitaus populärer als viele andere Flask-Plugins sein. Möglicherweise liegt es daran, dass die Dokumentation zu kompakt und abstrakt ist.

Das löste das Problem, YAML (eine andere Syntax) in Python-Docstrings schreiben zu müssen.