Joan Puigcerver 466ef6a132 Change the way that batching.spec_types is updated.
There's no reason why not two custom vmappable types cannot share the same spec_type. However, spec_types was a set, which can cause bugs / exceptions.

Suppose that I register two vmappable data_types sharing the same spec_type, and then unregister one of the two. Then, the spec_type is no longer in the set to support the second data_type. Also, an exception will be raised if I try to unregister the two vmappable types (the second call to spec_types.remove).

When unregistering a data type, instead of removing its spec_type from the set, we regenerate the set from the remaining vmappable types.

PiperOrigin-RevId: 737280270
2025-03-15 22:58:44 -07:00
..
2024-12-18 07:46:14 +00:00
2025-03-07 04:52:58 +00:00
2024-05-25 17:46:01 +00:00
2024-10-07 12:27:35 -07:00
2024-11-05 13:28:17 -08:00
2025-02-26 04:48:25 +00:00
2025-02-18 09:44:16 +00:00
2025-03-14 11:48:21 -07:00
2025-03-12 18:15:14 -04:00
2024-07-15 12:54:00 -07:00