This decoupling of parts, and being a "microframework" that could be extended to cover exactly what is needed was a key feature that I wanted to keep.

Given the simplicity of Flask, it seemed like a good match for building APIs. The next thing to find was a "Django REST Framework" for Flask.

/// check | Inspired **FastAPI** to

Be a micro-framework. Making it easy to mix and match the tools and parts needed.

Have a simple and easy to use routing system.

    Collections.addAll(set, elements);
    return set;
  }

  /**
   * Creates a <i>mutable</i> {@code HashSet} instance containing the given elements. A very thin
   * convenience for creating an empty set then calling {@link Collection#addAll} or {@link
   * Iterables#addAll}.
   *
   * <p><b>Note:</b> if mutability is not required and the elements are non-null, use {@link

      MockResponse(
        code = 503,
        headers = headersOf("Retry-After", "0"),
        body = "please retry",
      ),
    )
    server.enqueue(
      MockResponse(body = "thank you for retrying"),
    )
    val request =
      Request(
        url = server.url("/"),
        body =
          object : RequestBody() {
            var attempt = 0

and <i>w'</i> happens before <i>r</i>.
That is, each read must observe a value written by a preceding or concurrent write.
</p>

<p>
Additionally, observation of acausal and “out of thin air” writes is disallowed.
</p>

<p>
Reads of memory locations larger than a single machine word
are encouraged but not required to meet the same semantics
as word-sized memory locations,

    Collections.addAll(set, elements);
    return set;
  }

  /**
   * Creates a <i>mutable</i> {@code HashSet} instance containing the given elements. A very thin
   * convenience for creating an empty set then calling {@link Collection#addAll} or {@link
   * Iterables#addAll}.
   *
   * <p><b>Note:</b> if mutability is not required and the elements are non-null, use {@link

s390x // instruction for vector multiply high, low, and add, // since there aren't exact equivalent instructions. // The corresponding s390x instructions appear in the // comments. // Implementation for big endian would have to be // investigated, I think it would be different. // // // Vector multiply word // // VMLF x0, x1, out_low // VMLHF x0, x1, out_hi #define VMULT(x1, x2, out_low, out_hi) \ VMULEUW x1, x2, TMP1; \ VMULOUW x1, x2, TMP2; \ VMRGEW TMP1, TMP2, out_hi; \ VMRGOW TMP1, TMP2, out_low...

        }
    }
    throw new AssertionError("impossible");
  }

  /**
   * Returns the closest representable {@code long} to the absolute value of {@code x}.
   *
   * <p>This is the same thing as the true absolute value of {@code x} except in the case when
   * {@code x} is {@link Long#MIN_VALUE}, in which case this returns {@link Long#MAX_VALUE}. (Note

s390x // instruction for vector multiply high, low, and add, // since there aren't exact equivalent instructions. // The corresponding s390x instructions appear in the // comments. // Implementation for big endian would have to be // investigated, I think it would be different. // // // Vector multiply word // // VMLF x0, x1, out_low // VMLHF x0, x1, out_hi #define VMULT(x1, x2, out_low, out_hi) \ VMULEUW x1, x2, TMP1; \ VMULOUW x1, x2, TMP2; \ VMRGEW TMP1, TMP2, out_hi; \ VMRGOW TMP1, TMP2, out_low...

   * @Nullable X>, then users might pass a TypeParameter<Y>, where Y is a subtype of X, while still
   * passing a TypeToken<X>. This would be invalid. Maybe we could accept a TypeParameter<@PolyNull
   * X> if we support such a thing? It would be weird or misleading for users to be able to pass
   * `new TypeParameter<@Nullable T>() {}` and have it act as a plain `TypeParameter<T>`, but

what is explained in that document, and
describes the peculiarities that apply when writing assembly code to interact with Go.
</p>

<p>
The most important thing to know about Go's assembler is that it is not a direct representation of the underlying machine.
Some of the details map precisely to the machine, but some do not.
This is because the compiler suite (see