`StatsAggregator`. Add nested option, `experimental_stats` (which takes
        a `tf.data.experimen tal.StatsOptions` object), to `tf.data.Options`.
        Deprecates `tf.data.experimental.set_stats_agregator`.
    *   Performance optimizations:
    *   Add `tf.data.experimental.OptimizationOptions()`, to configure options
        to enable `tf.data` performance optimizations. Add nested option,

	PEXTRD $7, X2, (BX)                     // 660f3a161307
	PEXTRD $7, X11, (BX)                    // 66440f3a161b07
	PEXTRD $7, X2, (R11)                    // 66410f3a161307
	PEXTRD $7, X11, (R11)                   // 66450f3a161b07
	PEXTRD $7, X2, DX                       // 660f3a16d207
	PEXTRD $7, X11, DX                      // 66440f3a16da07
	PEXTRD $7, X2, R11                      // 66410f3a16d307

- Fixed a bug where executing a kubectl command with a jsonpath output expression that has a nested range would ignore expressions following the nested range. ([#88464](https://github.com/kubernetes/kubernetes/pull/88464), [@brianpursley](https://github.com/brianpursley)) [SIG API Machinery]

  }];

  let arguments = (ins
    Arg<TF_VariantTensor, [{A Tensor with type=DT_VARIANT containing the deduplication
data. The tensor is an XLA nested tuple containing N elements (where N is
the ratio of the number of embedding to tensor cores per TPU chip). Each
element of the nested tuple is a tuple of rank 1 tensors. Each tensor either
contains indices (DT_UINT32) for embedding lookup on the TensorCore or

		{"IpAdapterInfo.Next", Field, 0},
		{"IpAdapterInfo.PrimaryWinsServer", Field, 0},
		{"IpAdapterInfo.SecondaryWinsServer", Field, 0},
		{"IpAdapterInfo.Type", Field, 0},
		{"IpAddrString", Type, 0},
		{"IpAddrString.Context", Field, 0},
		{"IpAddrString.IpAddress", Field, 0},
		{"IpAddrString.IpMask", Field, 0},
		{"IpAddrString.Next", Field, 0},
		{"IpAddressString", Type, 0},

may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\".\n\nThis field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned...

            "type": "string"
          },
          "securityContext": {