/**
   * This field's name "only-if-cached" is misleading. It actually means "do not use the network".
   * It is set by a client who only wants to make a request if it can be fully satisfied by the
   * cache. Cached responses that would require validation (ie. conditional gets) are not permitted
   * if this header is set.
   */
  @get:JvmName("onlyIfCached") val onlyIfCached: Boolean,
  @get:JvmName("noTransform") val noTransform: Boolean,

 * descriptor ACEs:
 * <pre>
 * Allow WNET\alice     0x001200A9  Direct
 * Allow Administrators 0x001F01FF  Inherited
 * Allow SYSTEM         0x001F01FF  Inherited
 * </pre>
 * the access check would fail because the direct ACE has an access mask
 * of <code>0x001200A9</code> which doesn't have the
 * <code>FILE_WRITE_DATA</code> bit on (bit <code>0x00000002</code>). Actually, this isn't quite correct. If

        // When & Then - verify empty collection behavior
        assertFalse(emptyIterator.hasNext(), "Empty iterator should have no next element");

        // Note: Standard Iterator would throw NoSuchElementException, but this implementation returns null
        // This is a design choice for this specific implementation
        assertNull(emptyIterator.next(), "This implementation returns null instead of throwing");

    /*
     * Even though it's weird to pass a defaultValue that is null, some callers do so. Those who
     * pass a literal "null" should probably just use `get`, but I would expect other callers to
     * pass an expression that *might* be null. This could happen with:
     *
     * - a `getFooOrDefault(@Nullable Foo defaultValue)` method that returns
     *   `map.getOrDefault(FOO_KEY, defaultValue)`
     *

The application-layer must block on writing I/O. We can't return from a write until we've pushed its bytes onto the socket. Otherwise, if the write fails we are unable to deliver its IOException to the application. We would have told the application layer that the write succeeded, but it didn't!

   *
   * <p>For example, if {@code rangeMap} had the entries {@code [1, 5] => "foo", (6, 8) => "bar",
   * (10, ∞) => "baz"} then {@code rangeMap.subRangeMap(Range.open(3, 12))} would return a range map
   * with the entries {@code (3, 5] => "foo", (6, 8) => "bar", (10, 12) => "baz"}.
   *
   * <p>The returned range map supports all optional operations that this range map supports, except

  ContiguousSet<C> subSetImpl(
      C fromElement, boolean fromInclusive, C toElement, boolean toInclusive) {
    if (fromElement.compareTo(toElement) == 0 && !fromInclusive && !toInclusive) {
      // Range would reject our attempt to create (x, x).
      return new EmptyContiguousSet<>(domain);
    }
    return intersectionInCurrentDomain(
        Range.range(
            fromElement, BoundType.forBoolean(fromInclusive),

### Serverside Apply - Beta 2

   * old Android Ice Cream Sandwich release), then this method throws an exception instead of
   * creating a directory that would be more accessible. (This behavior is new in Guava 32.0.0.
   * Previous versions would create a directory that is more accessible, as discussed in <a
   * href="https://github.com/google/guava/issues/4011">CVE-2020-8908</a>.)
   *

        // Override purge to avoid client operations
        ThumbnailManager testManager = new ThumbnailManager() {
            @Override
            public long purge(long expiry) {
                // Just count files that would be deleted
                return 1L;
            }
        };
        testManager.baseDir = tempDir;

        long result = testManager.purge(1L);
        assertTrue(result >= 0); // Count of deleted files