Issues

• Relax acronym guidance for UpperSnakeCase identifiers

  rust-lang/api-guidelines#292 · Filter by author ds84182 opened on Aug 8, 2026

• question: can we make ai skills of these?

  rust-lang/api-guidelines#291 · Filter by author dzmitry-lahoda opened on Jul 1, 2026

• No links for API guidelines in docs

  rust-lang/api-guidelines#285 · Filter by author hecto600 opened on May 26, 2025

• Document the most common non-trait methods?

  rust-lang/api-guidelines#283 · Filter by author cher-nov opened on Nov 16, 2024

• Missing setter convention described in RFC344

  rust-lang/api-guidelines#279 · Filter by author duskmoon314 opened on May 23, 2024
  1

• C-CTOR: incorrect usage of term "method"

  rust-lang/api-guidelines#274 · Filter by author jnuss opened on Sep 29, 2023
  2

• C-COMMON-TRAITS favors implementing traits too eagerly

  rust-lang/api-guidelines#268 · Filter by author Enet4 opened on Aug 29, 2022

• C-STABLE too restrictive?

  rust-lang/api-guidelines#267 · Filter by author tobiasvl opened on Aug 16, 2022
  4

• Elaborate the C-DEREF guideline

  rust-lang/api-guidelines#257 · Filter by author NeverGivinUp opened on Dec 27, 2021
  1

• Mention the need to define a reasonable MSRV

  rust-lang/api-guidelines#252 · Filter by author estebank opened on Sep 17, 2021
  11

• C-DEREF contradicts idiomatic API in the standard library

  rust-lang/api-guidelines#249 · Filter by author matklad opened on Aug 23, 2021
  8

• C-WORD-ORDER when there is no verb

  rust-lang/api-guidelines#246 · Filter by author Kestrer opened on Jul 22, 2021

• C-CONV table is confusing regarding Copy types

  rust-lang/api-guidelines#245 · Filter by author Kixunil opened on Jun 21, 2021

• Naming for hidden items that have to be public

  rust-lang/api-guidelines#243 · Filter by author kgv opened on Jun 10, 2021

• C-LINK should encourage use of intra-rustdoc links over manual linking

  rust-lang/api-guidelines#241 · Filter by author ilyvion opened on May 22, 2021

• Mention 0BSD and/or MIT-0 among permissible licenses?

  rust-lang/api-guidelines#239 · Filter by author voxpelli opened on Mar 18, 2021
  4

• Reconsider C-STRUCT-BOUNDS

  amendment
  rust-lang/api-guidelines#217 · Filter by author Kixunil opened on Apr 3, 2020
  1

• is gitter channel the right place to direct people to for discussion?

  rust-lang/api-guidelines#215 · Filter by author ultrasaurus opened on Jan 22, 2020
  1

• Naming guidelines recommend into_iter() method instead of IntoIterator trait

  acceptedamendmentI-nominated
  rust-lang/api-guidelines#206 · Filter by author Aloso opened on Nov 14, 2019
  3

• C-STRUCT-PRIVATE guideline incomplete

  acceptedamendment
  rust-lang/api-guidelines#203 · Filter by author gnzlbg opened on Sep 25, 2019
  4

• C-QUESTION-MARK: Use simpler main error type syntax

  acceptedpresentation
  rust-lang/api-guidelines#201 · Filter by author SOF3 opened on Aug 10, 2019
  2

• C-CRATE-DOC should explain, not link

  acceptedamendmentI-nominated
  rust-lang/api-guidelines#188 · Filter by author ralfbiedert opened on Jan 21, 2019
  1

• Japanese translation

  rust-lang/api-guidelines#184 · Filter by author himanoa opened on Oct 11, 2018
  3

• C-CONV and C-CONV-TRAITS do not mention each other and are unclear

  amendmentI-nominated
  rust-lang/api-guidelines#175 · Filter by author orlp opened on Jul 10, 2018
  1

• Extend C-DEREF guideline to say smart pointers should always be transparent in Debug representation

  amendmentdisposition-mergefinished-final-comment-periodneeds-fcpT-libs
  rust-lang/api-guidelines#168 · Filter by author dtolnay opened on May 17, 2018
  7