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

Decide whether or not to have #[must_use] on PartialEq #43810

Closed
alexcrichton opened this issue Aug 11, 2017 · 1 comment
Closed

Decide whether or not to have #[must_use] on PartialEq #43810

alexcrichton opened this issue Aug 11, 2017 · 1 comment
Labels
C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.

Comments

@alexcrichton
Copy link
Member

This is a "tracking issue" sort for #[must_use] annotations added in #43728. Mostly this is a placeholder to ensure this comes up at the next libs triage meeting! the libs team will want to make a decision here one way or the other during the next triage meeting.
@alexcrichton alexcrichton added I-nominated T-libs-api Relevant to the library API team, which will review and decide on the PR/issue. labels Aug 11, 2017
@shepmaster shepmaster added the C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC label Aug 11, 2017
@alexcrichton
Copy link
Member Author

Discussed at libs triage conclusion was these are good to go!

@zackmdavis zackmdavis mentioned this issue Aug 28, 2017
Closed
# for free to join this conversation on GitHub. Already have an account? # to comment
Assignees
No one assigned
Labels
C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC T-libs-api Relevant to the library API 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 @shepmaster