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/4324#issuecomment-677882351,https://api.github.com/repos/pydata/xarray/issues/4324,677882351,MDEyOklzc3VlQ29tbWVudDY3Nzg4MjM1MQ==,1217238,2020-08-20T20:18:49Z,2020-08-20T20:18:49Z,MEMBER,"> I brought this up at the meeting, and if I remember correctly, the recommendation was to take a step back and solve nested duck arrays in general (e.g. by writing a design doc – a NEP?). Correct me if I'm wrong, @shoyer, but I think the hope was that after that it would be easier to design nested reprs.

I don't think that necessarily needs to be _blocker_ for this particular effort, but I do think this is an area where summarizing high level ideas into a ""design document"" that clearly articulates the use-cases and suggested solutions could be a good idea.

I don't know if this NEP necessarily needs to live in NumPy, but I do think the NEP template is a nice starting point for what should be covered in such a porposal: https://numpy.org/neps/nep-template.html","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,675342733