Anshul Singhvi

This works now but runs into the efficiency problems from ZarrDatasets.jl.

It's the same old CommonDataModel / DiskArrays slowness thing I think.

I'd also like the capability to instantiate a Raster from either a ZarrDataset or a Zarr array...I can probably implement this but commenting so I have somewhere to reference. What's...

@felixcremer mentioned on Slack that Zarr CRS specs are supposed to live in global metadata under a key. We should integrate that into the cf branch at some point.

In theory all this would take is a package extension on Chairmarks, which removes `run!` from whichever code extracts `SUITE`, and extracts statistics slightly differently...

Hmm, that also sounds like an interesting idea. Shouldn't be too hard to implement! That being said, what I wanted to do was the following: I have a benchmark suite...

A quick monkeypatch for my current issue is: ```julia @eval OpenApi.Clients is_json_mime(mime::T) where {T

Just wanted to bump this issue - what's the best way forward here?

possibly `startswith("application", string) && endswith("json", string)`, or maybe even `startswith("application", string) && occursin("json", string)`? I can whip up a quick PR once we settle on what the criterion should be...

I assume the MakiePlotter struct's definition is here, https://github.com/Ferrite-FEM/FerriteViz.jl/blob/0eeec9a8bf5ff8a51b88cff3ec9c8de43e07b8bf/src/utils.jl#L34-L48 and it looks like cells are triangulated and assembled here, https://github.com/Ferrite-FEM/FerriteViz.jl/blob/0eeec9a8bf5ff8a51b88cff3ec9c8de43e07b8bf/src/utils.jl#L63-L82 so maybe we could filter all line elements out of...