rust-lang/api-guidelines

Issues

• Document the most common non-trait methods?

  #283 opened 2 months ago by cher-nov
  0

• C-PERMISSIVE: Use automatic links

  #281 opened 5 months ago by axelkar
  0

• Missing setter convention described in RFC344

  #279 opened 8 months ago by duskmoon314
  1

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

  #168 opened 7 years ago by dtolnay
  7

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

  #274 opened a year ago by jnuss
  2

• C-COMMON-TRAITS favors implementing traits too eagerly

  #268 opened 2 years ago by Enet4
  0

• C-STABLE too restrictive?

  #267 opened 2 years ago by tobiasvl
  4

• C-PERMISSIVE and MPLv2

  #122 opened 3 years ago by RazrFalcon
  12

• Elaborate the C-DEREF guideline

  #257 opened 3 years ago by NeverGivinUp
  1

• Mention the need to define a reasonable MSRV

  #252 opened 3 years ago by estebank
  11

• C-DEREF contradicts idiomatic API in the standard library

  #249 opened 3 years ago by matklad
  8

• Justification of html_root_url is missing nuance

  #229 opened 3 years ago by jyn514
  24

• C-WORD-ORDER when there is no verb

  #246 opened 3 years ago by Kestrer
  0

• C-CONV table is confusing regarding Copy types

  #245 opened 4 years ago by Kixunil
  0

• Naming for hidden items that have to be public

  #243 opened 4 years ago by kgv
  0

• trivial typo

  #240 opened 4 years ago by kklibo
  0

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

  #241 opened 4 years ago by ilyvion
  0

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

  #239 opened 4 years ago by voxpelli
  4

• How to push request the translate docs

  #237 opened 4 years ago by shenshouer
  0

• Type macros may follow a different naming convention

  #145 opened 7 years ago by dtolnay
  9

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

  #206 opened 5 years ago by Aloso
  3

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

  #201 opened 5 years ago by SOF3
  2

• C-STRUCT-PRIVATE guideline incomplete

  #203 opened 5 years ago by gnzlbg
  4

• Render checklist as a checklist

  #131 opened 4 years ago by dtolnay
  1

• C-NEWTYPE-HIDE neglects to mention other traits implemented by the wrapped type

  #142 opened 7 years ago by chris-morgan
  1

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

  #175 opened 7 years ago by orlp
  1

• C-CRATE-DOC should explain, not link

  #188 opened 6 years ago by ralfbiedert
  1

• Add an appendix with links to the open "soliciting opinions" issues

  #141 opened 7 years ago by dtolnay
  3

• Don't use unstable syntax without some sort of parsing guard

  #156 opened 4 years ago by leoyvens
  1

• Crates which re-export types from other crates should also re-export the entire crate

  #170 opened 4 years ago by jsgf
  3

• What is the reason for `C-RW-VALUE`?

  #174 opened 4 years ago by tbu-
  4

• Reconsider C-STRUCT-BOUNDS

  #217 opened 5 years ago by Kixunil
  1

• traits in types are marked with dyn/impl, not bare

  #190 opened 4 years ago by lorepozo
  2

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

  #215 opened 5 years ago by ultrasaurus
  1

• Document recommendation about Arc::clone(&ref) syntax.

  #200 opened 4 years ago by nical
  1

• Test for Send/Sync/other traits with where Self: Send + Sync + ...

  #223 opened 4 years ago by Veetaha
  5

• Possible contradiction between the different conversion naming guidelines?

  #219 opened 5 years ago by arnauorriols
  3

• Broken link to the Rust FAQ

  #191 opened 5 years ago by mattheww
  3

• Move Repository To rust-lang

  #205 opened 5 years ago by XAMPPRocky
  1

• Japanese translation

  #184 opened 6 years ago by himanoa
  3

• Feature names cannot always be free of placeholder words

  #164 opened 7 years ago by rushmorem
  2

• The example for C-BITFLAGS is broken

  #160 opened 7 years ago by abusch
  0

• Naming convention for macros

  #135 opened 7 years ago by dtolnay
  3

• Error handling and quick-error (C-GOOD-ERR)

  #144 opened 7 years ago by tailhook
  2

• Guideline about extern crate

  #139 opened 7 years ago by AlexEne
  2

• Use the latest version of mdBook

  #129 opened 7 years ago by dtolnay
  1

• Headers should link to the #c-heading

  #136 opened 7 years ago by dtolnay
  0

• Combined guideline about documenting errors, panics, safety

  #133 opened 7 years ago by dtolnay
  1

• Mention get_unchecked_mut

  #134 opened 7 years ago by dtolnay
  1

• Auto-deploy does not work

  #120 opened 7 years ago by dtolnay
  4