interruptee.interrupt();
                Thread.yield();
              }
            }
          });
      this.shutdown = shutdown;
      start();
    }

    @SuppressWarnings("ThreadPriorityCheck") // TODO: b/175898629 - Consider onSpinWait.
    void shutdown() {
      shutdown.set(true);
      while (this.isAlive()) {
        Thread.yield();
      }
    }
  }

                        tree.acquire();
                        successCount.incrementAndGet();

                        // Small delay to increase chance of race conditions
                        Thread.yield();
                    }
                } catch (Exception e) {
                    exceptions.add(e);
                } finally {
                    endLatch.countDown();
                }
            });

                interruptee.interrupt();
                Thread.yield();
              }
            }
          });
      this.shutdown = shutdown;
      start();
    }

    @SuppressWarnings("ThreadPriorityCheck") // TODO: b/175898629 - Consider onSpinWait.
    void shutdown() {
      shutdown.set(true);
      while (this.isAlive()) {
        Thread.yield();
      }
    }
  }

          taskRunner: TaskRunner,
          nanos: Long,
        ) {
          taskRunner.assertLockHeld()
          check(waitingCoordinatorTask == null)
          if (nanos == 0L) return

          // Yield until notified, interrupted, or the duration elapses.
          val waitUntil = nanoTime + nanos
          val self = currentTask
          waitingCoordinatorTask = self
          waitingCoordinatorNotified = false

{* ../../docs_src/custom_response/tutorial008.py hl[2,10:12,14] *}

1. 이것이 제너레이터 함수입니다. `yield` 문을 포함하고 있으므로 "제너레이터 함수"입니다.
2. `with` 블록을 사용함으로써, 제너레이터 함수가 완료된 후 파일과 같은 객체가 닫히도록 합니다. 즉, 응답 전송이 끝난 후 닫힙니다.
3. 이 `yield from`은 함수가 `file_like`라는 객체를 반복(iterate)하도록 합니다. 반복된 각 부분은 이 제너레이터 함수(`iterfile`)에서 생성된 것처럼 `yield` 됩니다.

    이렇게 하면 "생성(generating)" 작업을 내부적으로 다른 무언가에 위임하는 제너레이터 함수가 됩니다.

            t = (date.getTime() + SmbConstants.MILLISECONDS_BETWEEN_1970_AND_1601) * 10000L;
            yield enc_uint64be(t, dst, di);
        }
        case TIME_1601_NANOS_64LE -> {
            t = (date.getTime() + SmbConstants.MILLISECONDS_BETWEEN_1970_AND_1601) * 10000L;
            yield enc_uint64le(t, dst, di);
        }
        case TIME_1970_MILLIS_64BE -> enc_uint64be(date.getTime(), dst, di);

        case TIME_1601_NANOS_64BE -> {
            t = (date.getTime() + MILLISECONDS_BETWEEN_1970_AND_1601) * 10000L;
            yield enc_uint64be(t, dst, di);
        }
        case TIME_1601_NANOS_64LE -> {
            t = (date.getTime() + MILLISECONDS_BETWEEN_1970_AND_1601) * 10000L;
            yield enc_uint64le(t, dst, di);
        }
        case TIME_1970_MILLIS_64BE -> enc_uint64be(date.getTime(), dst, di);

2. Al usar un bloque `with`, nos aseguramos de que el objeto similar a un archivo se cierre después de que la función generadora termine. Así, después de que termina de enviar el response.
3. Este `yield from` le dice a la función que itere sobre esa cosa llamada `file_like`. Y luego, para cada parte iterada, yield esa parte como proveniente de esta función generadora (`iterfile`).

1. This is the generator function. It's a "generator function" because it contains `yield` statements inside.
2. By using a `with` block, we make sure that the file-like object is closed after the generator function is done. So, after it finishes sending the response.
3. This `yield from` tells the function to iterate over that thing named `file_like`. And then, for each part iterated, yield that part as coming from this generator function (`iterfile`).

                        "timed out waiting for other threads to block"
                            + " synchronizing on supplier"));
                break;
              }
              Thread.yield();
            }
            count.getAndIncrement();
            return Boolean.TRUE;
          }
        };

    Supplier<Boolean> memoizedSupplier = memoizer.apply(supplier);