Rafael Schouten

`Y` is mostly actually just `Y`/`Lat`/`Lon` (macro generated types) to avoid the ugly `Dim{:x}` syntax, although you can use that too. They're also not singletons! they hold ranges/arrays and metadata...

Bump. If I put together a pull request removing `::Integer` from some dims kwargs (mostly in accumulate.jl) would it be accepted? Also would adding dispatchable `_methods` for cov, cor and...

Sure. It wont break anything, just type loosenong and some extra intermediate methods without kwargs. I'll make a pull request.

I'm looking into using the methods in this package in DimensionalData.jl/GeoData.jl - when there is a time dimension present, as in AxisArrays.jl. Often we have multidimensional arrays where time is...

It does seem like a real ambiguity But oddly it wasn't an ambiguity before now, and those methods are 3 and 4 years old. Aqua.jl also hasn't had an update...

Probably, I have no idea how Aqua.jl actually tests ambiguity :laughing:

We try not to change base method signatures besides allowing `dims` to be named. To keep the mental model very simple. I would just put that new `Dimension` in `dims`...

Using a `Pair` sounds like a good solution (as do points 1 and 2 as simpler cases). For 2 I guess putting it as the last dimension would be the...

That would really be moving away from base julia behavior. We actually never automatically permute or do anything fancy like that on Base methods so we don't accidentally let through...

Can you just `permute` all your arrays to a particular dim order first?