html_url,issue_url,id,node_id,user,created_at,updated_at,author_association,body,reactions,performed_via_github_app,issue
https://github.com/pydata/xarray/issues/4285#issuecomment-1254775144,https://api.github.com/repos/pydata/xarray/issues/4285,1254775144,IC_kwDOAMm_X85Kyllo,88113,2022-09-22T09:36:26Z,2022-09-22T09:36:26Z,NONE,"Definitely interested and interestedly watching 🍿 

> [jpivarski](https://github.com/jpivarski) commented [on Aug 10](https://github.com/pydata/xarray/issues/4285#issuecomment-1210023820) It shouldn't be a subclass because it doesn't satisfy a substitution principle: ak.combinations(array: ak.Array, n: int) -> ak.Array, but ak.combinations(array: RaggedArray, n: int) -> ⊥ (at best, would raise an exception because RaggedArray isn't closed under ak.combinations).

A question from the perspective of Zarr (v3), does it make sense to think of this potential `RaggedArray` as a base extension that `AwkwardArray` could then build on top of? (i.e. the reverse) Or more something to keep separate and it's just a matter of the same library could be used to read (de/serialize) either?


More generally, :heart: for all of this, and interested to see how I/we can possibly help.
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,667864088