Hide some implementation details from docs

[sivadeilra]

This adds #[doc(hidden)] to several generated items: the vtable
statics for classes, the IID for interfaces, and a type alias.

This makes cargo doc a lot cleaner.

[rylev]

I agree with 2 of the 3 items being hidden, but I think the IID should be left. Thoughts?

[rylev]

This seems less like an implementation detail than the other items. I can certainly imagine someone wanting to directly use an interfaces IID. Are we sure we want this to be hidden?

[MarijnS95]

I agree with 2 of the 3 items being hidden, but I think the IID should be left. Thoughts?

I don't use the docs all that much, but I agree that seems the only thing I'd like to keep.

Afaik com-rs generates function-call helpers for everything so that the user should never touch the vtable manually. On the other hand, certain APIs require an iid+ppv pair to return the desired COM object, and I don't think com-rs hides that in the same way that windows-rs does it currently (by using a type argument and reading T::IID from it)?

[sivadeilra]

I think using IFoo::IID or <IFoo as Interface>::IID is better than using IID_IFOO.

[rylev]

I think using IFoo::IID or <IFoo as Interface>::IID is better than using IID_IFOO.

You're right. Ok Let's merge this then.

[MarijnS95]

I think using IFoo::IID or <IFoo as Interface>::IID is better than using IID_IFOO.

Oh I hadn't read that this is the "static global" declaration, not the associated member on IFoo when implementing the Interface trait. Then this is actually a great nudge to just use that instead 👌