Rafael Schouten

Also FYI https://github.com/Keno/InterfaceSpecs.jl Keno doesn't seem to care about using `return_type` and similar things either As far as I can tell it doesn't produce no-cost traits, it just the tests...

Good question! I've been thinking about it but haven't settled on something yet. We have abstract types already, so traits can work based on subtyping. All the test components of...

Well, its really a precompile time thing ;) It may never be that widespread as a runtime dependency. But I think some package that does this needs to be, so...

Thats what we have! The trait is just a compile time binary that the interface is implemented. But the macro forces the trait to be tested during precompilation, so the...

Yes, probably it will be too slow. The option is to define the interface structure at runtime and fill it out in InterfaceTests.jl. That will just take a little longer...

There should be an easy way to have tests and traits compiled separately but have them linked. Just defing the interface list components at runtime has no overhead. Then we...

#8. Running tests in the test suite is enough.

Yes, it would great to have this, probably as part of JuliaGeo. I havent had time so far, but I can assist with reviews etc if anyone else does.

Yes. Remove `::Integer` from some kwarg dim types, and add wrapper `_cov(X, dims)` etc methods that can use multiple dispatch on dims, where they are missing. `dims::Integer` can go on...

Thanks that's an interesting aproach. In DimensionalData.jl it's `sum(x; dims=Y)`. Specifying the order with `along(x, &, &, :)` is kind of an antipattern with named dimensions, but `sum(along(x, Y))` would...