tree 35d017aca4c602e8c9a0e8e455195fbd75fdbd91
parent 2b5e61f7d1c387343ca99672bf274f4cf8d2f162
author bjacob <benoitjacob@google.com> 1697487293 -0400
committer GitHub <noreply@github.com> 1697487293 -0400
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJlLZm9CRBK7hj4Ov3rIwAAus8IAB/dsfyaFYni8yQNot//zXQC
 kAt4nDnTX5tc+tR6JlsXQREB+sreWckbpv2JI4qzUz1JB+KYBYUyvJ0oTbP59B3K
 O1G5ozAFHMWXevCh3SuQqGq+B+JkTY7E3pBGstV4ODNDvfeBUOIt9B5iXb0uGaJE
 7AzsvgOYTMicU4GTCd9/BxyvnDBzZwDTFri/TUFMZs7/pHDrDQYZr25j+0ED1TMM
 6U6cAZ4UDKu7HH4VuJ9gwLr7AdB15+QhF6+duy5NEAlr+LpAKn7jCuPgH2z84pX6
 b0ZHOwvZPPAtrTrMpTk5wp9FYTxVOBD0NQO5na4kMcCD6uJJ9PZFxmnYj7BJMVc=
 =oYrR
 -----END PGP SIGNATURE-----
 

Data-tiling encodings: take the element types out of the enums. (#15182)

This has been discussed for a while: ever since #14336 made encodings a
data structure, it was an odd remnant that we were still encoding the
element types tuple in the user enum. This was cumbersome, and
resurfaced in every design discussion as it looked like something that
wasn't scaling with new data types. Concretely, this is good to fix
ahead of adding `i16xi16` and `i16xi4` data-tiling support (#15158).