# Type/trait alias docs

**URL:** <https://users.rust-lang.org/t/type-trait-alias-docs/43901>\
**Category:** uncategorized\
**Created:** [June 6, 2020, 1:09pm UTC](https://users.rust-lang.org/t/type-trait-alias-docs/43901 "2020-06-06T13:09:36Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![burdges](https://sea1.discourse-cdn.com/flex019/user_avatar/users.rust-lang.org/burdges/32/6335_2.png) [@burdges](https://users.rust-lang.org/u/burdges)\
**Post date:** [June 6, 2020, 1:09pm UTC](https://users.rust-lang.org/t/type-trait-alias-docs/43901/1 "2020-06-06T13:09:36Z")

</div>

I've some type aliases for which I'd love the underlying type's methods to appear on the type alias.

```rust
pub type VRFSignature<E: JubjubEngine, PD>
 = VRFProof<E: JubjubEngine, VRFPreOut<E>, Individual<E>, PD>;

```

I've a couple methods polymorphic over `E` and `PD` that should really appear on this type alias, as well as on the underlying `VRFProof` type.

Assuming `E` fixed, there are roughly twelve possible types here, for which I'd love some good way to document each variant, although most do not require a trait alias since the user only touches them in passing, so transient builder states. In most cases, I'd place deeper documentation onto each viable type argument value, but embedding some discussion help. Is there some way to make doc comments on `impl` blocks appear?

---

<div class="post-metadata">

**Author:** ![system](https://sea1.discourse-cdn.com/flex019/user_avatar/users.rust-lang.org/system/32/51372_2.png) [@system](https://users.rust-lang.org/u/system)\
**Post date:** [September 4, 2020, 1:19pm UTC](https://users.rust-lang.org/t/type-trait-alias-docs/43901/2 "2020-09-04T13:19:42Z")

</div>

Closed on September 4, 2020, 1:19pm UTC

This topic was automatically closed 90 days after the last reply. We invite you to open a new topic if you have further questions or comments.