Skip to content

Issues: rust-lang/api-guidelines

New issue

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

Sign up for GitHub

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

Already on GitHub? Sign in to your account

29 Open 104 Closed
29 Open 104 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Document the most common non-trait methods?
#283 opened Nov 16, 2024 by cher-nov
C-PERMISSIVE: Use automatic links
#281 opened Jul 31, 2024 by axelkar
Missing setter convention described in RFC344
#279 opened May 23, 2024 by duskmoon314
1
C-CTOR: incorrect usage of term "method"
#274 opened Sep 29, 2023 by jnuss
2
C-COMMON-TRAITS favors implementing traits too eagerly
#268 opened Aug 29, 2022 by Enet4
C-STABLE too restrictive?
#267 opened Aug 16, 2022 by tobiasvl
4
Elaborate the C-DEREF guideline
#257 opened Dec 27, 2021 by NeverGivinUp
1
Mention the need to define a reasonable MSRV
#252 opened Sep 17, 2021 by estebank
11
C-DEREF contradicts idiomatic API in the standard library
#249 opened Aug 23, 2021 by matklad
1
8
C-WORD-ORDER when there is no verb
#246 opened Jul 22, 2021 by Kestrer
C-CONV table is confusing regarding Copy types
#245 opened Jun 21, 2021 by Kixunil
Naming for hidden items that have to be public
#243 opened Jun 10, 2021 by kgv
C-LINK should encourage use of intra-rustdoc links over manual linking
#241 opened May 22, 2021 by ilyvion
Mention 0BSD and/or MIT-0 among permissible licenses?
#239 opened Mar 18, 2021 by voxpelli
4
Reconsider C-STRUCT-BOUNDS amendment Amendments to existing guidelines
#217 opened Apr 3, 2020 by Kixunil
1
is gitter channel the right place to direct people to for discussion?
#215 opened Jan 22, 2020 by ultrasaurus
1
Naming guidelines recommend into_iter() method instead of IntoIterator trait accepted An amendment that's been accepted and can be applied amendment Amendments to existing guidelines I-nominated Indicates that an issue has been nominated for discussion during a team meeting.
#206 opened Nov 14, 2019 by Aloso
3
C-STRUCT-PRIVATE guideline incomplete accepted An amendment that's been accepted and can be applied amendment Amendments to existing guidelines
#203 opened Sep 25, 2019 by gnzlbg
4
C-QUESTION-MARK: Use simpler main error type syntax accepted An amendment that's been accepted and can be applied presentation
#201 opened Aug 10, 2019 by SOF3
2
C-CRATE-DOC should explain, not link accepted An amendment that's been accepted and can be applied amendment Amendments to existing guidelines I-nominated Indicates that an issue has been nominated for discussion during a team meeting.
#188 opened Jan 21, 2019 by ralfbiedert
1
Japanese translation
#184 opened Oct 11, 2018 by himanoa
3
C-CONV and C-CONV-TRAITS do not mention each other and are unclear amendment Amendments to existing guidelines I-nominated Indicates that an issue has been nominated for discussion during a team meeting.
#175 opened Jul 10, 2018 by orlp
1
Extend C-DEREF guideline to say smart pointers should always be transparent in Debug representation amendment Amendments to existing guidelines disposition-merge This issue / PR is in PFCP or FCP with a disposition to merge it. finished-final-comment-period The final comment period is finished for this PR / Issue. needs-fcp This change is insta-stable, so needs a completed FCP to proceed. T-libs Relevant to the libraries subteam, which will review and decide on the PR/issue.
#168 opened May 17, 2018 by dtolnay
7
Type macros may follow a different naming convention amendment Amendments to existing guidelines disposition-merge This issue / PR is in PFCP or FCP with a disposition to merge it. finished-final-comment-period The final comment period is finished for this PR / Issue. needs-fcp This change is insta-stable, so needs a completed FCP to proceed. T-libs Relevant to the libraries subteam, which will review and decide on the PR/issue.
#145 opened Nov 11, 2017 by dtolnay
9
C-NEWTYPE-HIDE neglects to mention other traits implemented by the wrapped type accepted An amendment that's been accepted and can be applied amendment Amendments to existing guidelines
#142 opened Nov 8, 2017 by chris-morgan
1
ProTip! Type g i on any issue or pull request to go back to the issue listing page.