Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Jump to bottom

Rustdoc should mention OIBIT-derived Send/Sync impls #25896

Closed
Manishearth opened this issue May 30, 2015 · 1 comment
Closed

Rustdoc should mention OIBIT-derived Send/Sync impls #25896

Manishearth opened this issue May 30, 2015 · 1 comment
Labels
C-enhancement Category: An issue proposing an enhancement or a PR with one. T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue.

Comments

@Manishearth
Copy link
Member

The rustdoc output only mentions Send/Sync impls for types which explicitly opt in or opt out.

There's no easy way to figure out when something is Send/Sync otherwise, and it's misleading when it seems like most types aren't Send/Sync.

Perhaps it should autogenerate an impl when OIBIT does so internally? Type param bounds might be hard to handle though.

cc @alexcrichton
@Manishearth Manishearth added T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue. C-enhancement Category: An issue proposing an enhancement or a PR with one. labels May 30, 2015
@alexcrichton
Copy link
Member

Dupe of #17606

# for free to join this conversation on GitHub. Already have an account? # to comment
Assignees
No one assigned
Labels
C-enhancement Category: An issue proposing an enhancement or a PR with one. T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@alexcrichton @Manishearth