*   Include unit tests when you contribute new features, as they help to a)
    prove that your code works correctly, and b) guard against future breaking
    changes to lower the maintenance cost.
*   Bug fixes also generally require unit tests, because the presence of bugs
    usually indicates insufficient test coverage.
*   Keep API compatibility in mind when you change code in core TensorFlow,
    e.g., code in

cc_library(
    name = "conversion_macros",
    hdrs = [
        "conversion_macros.h",
    ],
    visibility = ["//tensorflow:__subpackages__"],
)

cc_library(
    name = "c_op_requires",
    hdrs = ["c_op_requires.h"],
    visibility = ["//visibility:public"],
    deps = ["//tensorflow/core/platform:macros"],

        "@com_google_absl//absl/memory",
        "@com_google_absl//absl/strings:str_format",
        "@local_xla//xla/tsl/c:tsl_status_internal",
    ],
    alwayslink = 1,
)

filegroup(
    name = "pywrap_required_hdrs",
    srcs = [
        "abstract_context.h",
        "abstract_function.h",
        "abstract_op_attrs.h",
        "abstract_operation.h",
        "abstract_tensor_handle.h",
        "c_api.h",

  # This creates a list of targets under //tensorflow that are required for
  # TensorFlow python tests.
  bazel query --keep_going "deps($(cat $BATS_TEST_TMPDIR/deps), 1)" | grep "^//tensorflow" | grep -v -f $BATS_TEST_TMPDIR/ignore_these_deps | sort -u > $BATS_TEST_TMPDIR/required_deps


  # Find if any required dependencies are missing from the list of dependencies
  # included in the pip package.

  # This creates a list of targets under //tensorflow that are required for
  # TensorFlow python tests.
  bazel cquery --keep_going "deps($(cat $BATS_TEST_TMPDIR/deps), 1)" | grep "^//tensorflow" | grep -v -f $BATS_TEST_TMPDIR/ignore_these_deps | sort -u > $BATS_TEST_TMPDIR/required_deps


  # Find if any required dependencies are missing from the list of dependencies
  # included in the pip package.