typedef pulled from a private base doesn't appear in documentation

[correaa]

I have this directive inside a class:

https://gitlab.com/correaa/boost-multi/-/blob/develop/include/boost/multi/array_ref.hpp#L251

struct A : private layout_type {
...
	using typename layout_type::extent_type;
};

This type doesn't appear in the documentation, even though it's now public.

https://correaa.gitlab.io/boost-multi/multi/reference/boost/multi/array-0ad.html

I know I can put this in a different way so it appears in the documentation (using extent_type = layout_type::extent_type;), and I will do this as a workaround.

[alandefreitas]

Hi! Sorry. I'm not able to visualize what a minimal example would be. I think it's because the explanation is about something that doesn't exist, so I don't know exactly what should exist. 😅

Oh... Nevermind. Got it. Yes. It's definitely a bug although I have no idea what should be rendered there.

[correaa]

Yeah, it is tricky. Especially tricky because the system has to determine whether (in the example) extent_type is a function or a type.

Heroically, MrDocs could understand this as if it were using extent_type = typename layout_type::extent_type;, but I did this manually anyway.

Perhaps it deserves another category in the docs, I don't know.
Members/Types/"Usings" :)

For types, it is almost trivial to transform one representation into the other.

For functions, it is trickier (one would need to forward one function into the other).

I have many examples of functions enabled in derived classes in this way, but I didn't stumble upon an omission like this one.

Thanks,
Alfredo