* A PR should have a specific use case that it is solving.

* If the PR is for a feature, it should have docs.
    * Unless it's a feature we want to discourage, like support for a corner case that we don't want users to use.

        }
        return true;
    }

    /**
     * Converts an array to an object array ({@literal Object[]}).
     * <p>
     * The source array can be a primitive array. In that case, the resulting array will contain the corresponding wrapper types.
     * </p>
     *
     * @param array
     *            the array
     * @return the object array
     */

  }

  /*
   * ConcurrentMap operations which we may eventually add.
   *
   * The problem with these is that remove(K, long) has to be done in two phases by definition ---
   * first decrementing to zero, and then removing. putIfAbsent or replace could observe the
   * intermediate zero-state. Ways we could deal with this are:
   *
   * - Don't define any of the ConcurrentMap operations. This is the current state of affairs.
   *

            pkgs += "|jcifs.smb1";
            System.setProperty("java.protocol.handler.pkgs", pkgs);
        }
    }

    // supress javadoc constructor summary by removing 'protected'
    Config() {
    }

    /**
     * Set the default properties of the static Properties used by <code>Config</code>. This permits

   * separator}. For example, {@code join("-", 1, 2, 3)} returns the string {@code "1-2-3"}.
   *
   * @param separator the text that should appear between consecutive values in the resulting string
   *     (but not at the start or end)
   * @param array an array of unsigned {@code long} values, possibly empty
   */
  public static String join(String separator, long... array) {
    checkNotNull(separator);

        if (!preserveModelVersion) {
            /*
             * If the <build> contains <source> elements, it is not compatible with the Maven 4.0.0 model.
             * Remove the full <build> element instead of removing only the <sources> element, because the
             * build without sources does not mean much. Reminder: this removal can be disabled by setting

(kernel or iptables versions are insufficient), the kube-proxy will fall-back
to userspace mode. Kube-proxy is much more performant and less
resource-intensive in ‘iptables’ mode.
  * Node stability can be improved by reserving [resources](https://github.com/kubernetes/kubernetes/blob/release-1.2/docs/proposals/node-allocatable.md) for the base operating system using --system-reserved and --kube-reserved Kubelet flags

        \
        Write-Host 'Installing/updating packages...'; \
        & $installDir\python.exe -m pip install --upgrade setuptools packaging; \
        \
        Write-Host 'Removing installation binary...'; \
        Remove-Item C:\tmp\pyinstall.exe -Force; \
    }; \
    Write-Host 'Installing multiple Python versions...'; \
    $versions = @( \
        @{ version = '3.9.13'; prependPath = 0 }, \

 * retrieved from the artifact descriptor of the root dependency. And last, only direct dependencies can be specified in
 * which case the root node of the resulting graph has no associated dependency.
 *
 * @since 4.0.0
 */
@Experimental
@Immutable
public interface DependencyResolverRequest extends RepositoryAwareRequest {

    enum RequestType {
        COLLECT,

為何選擇 raise 例外而非回傳值的好處，會在相依性與安全性章節更為明顯。

在這個範例中，當用戶端以不存在的 ID 請求項目時，raise 一個狀態碼為 `404` 的例外：

{* ../../docs_src/handling_errors/tutorial001_py310.py hl[11] *}

### 回應結果 { #the-resulting-response }

如果用戶端請求 `http://example.com/items/foo`（`item_id` 為 `"foo"`），會收到 200 的 HTTP 狀態碼，以及以下 JSON 回應：

```JSON
{
  "item": "The Foo Wrestlers"
}
```