*       identically to {@code Nullable}</a> as of version 0.9.9.
 *   <li><a href="https://developers.google.com/j2objc">J2ObjC</a>, maybe: It might no longer be
 *       necessary there, since we have stopped using the {@code @ParametersAreNonnullByDefault}
 *       annotations that {@code ParametricNullness} was counteracting.
 * </ul>
 *

 *       identically to {@code Nullable}</a> as of version 0.9.9.
 *   <li><a href="https://developers.google.com/j2objc">J2ObjC</a>, maybe: It might no longer be
 *       necessary there, since we have stopped using the {@code @ParametersAreNonnullByDefault}
 *       annotations that {@code ParametricNullness} was counteracting.
 * </ul>
 *

previous build will be preserved and reused for the subsequent builds.

### Specifying Python dependencies

During bazel build all TensorFlow's Python dependencies are pinned to their
specific versions. This is necessary to ensure reproducibility of the build.
The pinned versions of the full transitive closure of TensorFlow's dependencies
together with their corresponding hashes are specified in
`requirements_lock_<python version>.txt` files (e.g.

   */
  @Override
  protected void expectContents(Collection<E> expectedCollection) {
    List<E> expectedList = copyToList(expectedCollection);
    // Avoid expectEquals() here to delay reason manufacture until necessary.
    if (getList().size() != expectedList.size()) {
      fail("size mismatch: " + reportContext(expectedList));
    }
    for (int i = 0; i < expectedList.size(); i++) {
      E expected = expectedList.get(i);

 * and request tracing capabilities.
 *
 * <p>Each request is associated with a {@link ProtoSession} that contains the configuration
 * and context necessary for request processing, including:
 * <ul>
 *   <li>User and system properties for interpolation</li>
 *   <li>Session start time information</li>
 *   <li>Project directory structures</li>
 * </ul>
 *

can be set on the command line. For example,

	GOOS=ios GOARCH=amd64 CGO_ENABLED=1 CC=$(go env GOROOT)/misc/ios/clangwrap.sh go build

Setting CC is not necessary if the toolchain is built with CC_FOR_TARGET set.

To use the go tool to run individual programs and tests, put $GOROOT/bin into PATH to ensure
the go_ios_$GOARCH_exec wrapper is found. For example, to run the archive/tar tests:

 *       identically to {@code Nullable}</a> as of version 0.9.9.
 *   <li><a href="https://developers.google.com/j2objc">J2ObjC</a>, maybe: It might no longer be
 *       necessary there, since we have stopped using the {@code @ParametersAreNonnullByDefault}
 *       annotations that {@code ParametricNullness} was counteracting.
 * </ul>
 *

 *       identically to {@code Nullable}</a> as of version 0.9.9.
 *   <li><a href="https://developers.google.com/j2objc">J2ObjC</a>, maybe: It might no longer be
 *       necessary there, since we have stopped using the {@code @ParametersAreNonnullByDefault}
 *       annotations that {@code ParametricNullness} was counteracting.
 * </ul>
 *

 *       identically to {@code Nullable}</a> as of version 0.9.9.
 *   <li><a href="https://developers.google.com/j2objc">J2ObjC</a>, maybe: It might no longer be
 *       necessary there, since we have stopped using the {@code @ParametersAreNonnullByDefault}
 *       annotations that {@code ParametricNullness} was counteracting.
 * </ul>
 *

 *       identically to {@code Nullable}</a> as of version 0.9.9.
 *   <li><a href="https://developers.google.com/j2objc">J2ObjC</a>, maybe: It might no longer be
 *       necessary there, since we have stopped using the {@code @ParametersAreNonnullByDefault}
 *       annotations that {@code ParametricNullness} was counteracting.
 * </ul>
 *