Skip to content

Conversation

danieleades
Copy link
Contributor

No description provided.

@dwrensha
Copy link
Member

This trait appears in user-facing API here:

T: IntoInternalListReader<'a>,

After this change, the private ListReader type would appear there instead, which I would prefer not to expose in such an API. I don't want users clicking on documentation links trying to understand this function, and ending up in the capnp::private namespace, where they usually don't need to be.

I've added a bit of documentation here: 636e4d5

@danieleades
Copy link
Contributor Author

This trait appears in user-facing API here:

T: IntoInternalListReader<'a>,

After this change, the private ListReader type would appear there instead, which I would prefer not to expose in such an API. I don't want users clicking on documentation links trying to understand this function, and ending up in the capnp::private namespace, where they usually don't need to be.

I've added a bit of documentation here: 636e4d5

Can you not hide the type using #[doc(hidden)]?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants