Rafael Schouten

Thanks, yes we should test on `OffsetArray`. Correctness fixes are probably more important at this stage, the cost of wrong stride in Array will be lost in the cost of...

Ugg not exactly it was Rasters.jl on main and its on a rebase branch of your NCDatasets.jl fork but just using your branch and DiskArrays 0.4 should be enough. Heres...

There are a few ways. `@test @inferred ` can help but wont always pick up internal type stability problems that never escape the function. Checking `@test (@allocations f(x)) == 0`...

Theres also @test_call in JET but it often returns too many things to be useful https://aviatesk.github.io/JET.jl/dev/jetanalysis/#JET.@test_call

`map` is actually broken in a _lot_ of ways, not just `collect_similar` I'm keen to try my very old idea of caching a whole column of chunks for `iterate` instead...

Does `map` work in DiskArrayEngine ? It just seems to me that we are silently returning the _wrong answer_ for map currently, which is worse than OOM errors. I am...

We are also using the `@assume_effects` macro so it wont work on 1.6 anyway. I think we need to bump ArchGDAL to 1.9. I already did this for a bunch...

DiskArrays is lying! 😂 We need a PR fixing the DidkArrays julia version to 1.9 and also testing on 1.9.

We need to yank 0.4.0 add a line with `yanked = true` below the 0.4.0 entry here: https://github.com/JuliaRegistries/General/blob/26a799dd08b207d2d8d3ce91d4575b8cec2b569f/D/DiskArrays/Versions.toml#L122

I'm pestering people on slack, see if they respond. People have been doing unnecessary yanks and Pkg isn't good at handling it, but this is a very legitimate use case.