The AbstractArray interface also encompasses the meaning of the type parameters: MyArray{T,N} has eltype T and dim N. A trait LikeArray ought to contain these two type parameters also, which in this context are associated types (at least Rust uses this term). Maybe this could be written as `TraitAbstractAr

The autogenerated API documentation for Pyface is missing a number of key details because some (many? all?) of its traits are documented with a regular # comment instead of a #: traits doc-comment that can be picked up by the trait documenter. It would be nice to fix that.

The particular instance that I ran into was trying to refer to IEditor.obj from 3rd party documentation (via intersph

Hi Taine,

In one of your example, you have

@trait Addable{L, R} begin
    (+) :: [L, R] => Any
    (+) = Base.:+
end

I'd like to do something like this, but avoid the Any. I was thinking something like

@trait Addable{L, R, X} where {X = inferAddable(L,R)} begin
    (+) :: [L, R] => X
    (+) = Base.:+
end

But then I'm having trouble getting the `@i

ConfigTrait was implemented here atk4/core#86, but there are no docs for it.

Explain better the difference between the list of aravo and the different data.frames.

Explain also better the different format of data (show pictures) between stack and non-stack.

The plain-text docstrings (i.e. accessed from ipython) are sometimes hard to read due to sphinx formatting. A small aspect of this was addressed in response to this issue here: seequent/properties#8 but overall, docs are still sphinx through-and-through.

It would be great to enable easier to read docs with Napolen - https://sphinxcontrib-napoleon.readthedocs.io/en/late