Giters
rust-lang
/
rust-guidelines
This repository has moved
Geek Repo:
Geek Repo
Github PK Tool:
Github PK Tool
Stargazers:
181
Watchers:
30
Issues:
31
Forks:
30
rust-lang/rust-guidelines Issues
Take down https://aturon.github.io/?
Updated
7 years ago
Dead url to builder objects
Closed
8 years ago
Broken link
Closed
8 years ago
Comments count
1
Trailing commas
Closed
8 years ago
Comments count
3
Indent 2 levels for line continuations
Closed
8 years ago
Comments count
1
Always separately bind RAII guards: Use scope instead of explicit drop.
Updated
9 years ago
Comments count
11
the intpocalypse
Updated
9 years ago
Comments count
2
Specific associated types: Foo<Bar=Baz> or Foo<Bar = Baz>?
Updated
9 years ago
Comments count
4
Conversion chapter should be updated with generic conversion traits
Updated
9 years ago
Remove reference to NoSend in the concurrency guide
Closed
10 years ago
Comments count
1
Style of if expressions used as ternary operators?
Updated
10 years ago
Comments count
3
Style guide should define whether or not to use abbreviations in error messages (e.g."can't" vs "can not")
Updated
10 years ago
Comments count
2
Mixed content on github.io
Closed
10 years ago
Comments count
1
Alignment for match expressions
Updated
10 years ago
Comments count
1
recommendation to use only line comments not justified
Updated
10 years ago
Comments count
2
"Never unwrap a Result for unavoidable errors" is confusing
Closed
10 years ago
Comments count
4
integer type style guidelines
Updated
10 years ago
Comments count
10
identifiable markers
Updated
10 years ago
Tag accepted conventions with relevant RFC
Updated
10 years ago
Error handling
Updated
10 years ago
Comments count
2
Order of imports and order of trait bounds
Updated
10 years ago
Comments count
2
How to fix the syntax highlighting of rust code ...
Closed
10 years ago
Comments count
1
move from gitbook to something homegrown
Closed
10 years ago
Comments count
4
Clarify where imports should be placed
Updated
10 years ago
Comments count
1
Structure rust-guidelines to make code easily accessible
Updated
10 years ago
Comments count
4
Moving braces to the next line increases readability in some situations
Updated
10 years ago
Comments count
6
Spaces around braces
Updated
10 years ago
Comments count
1
Make code snippets testable
Updated
10 years ago
kebab-case should be discouraged for crate names
Closed
10 years ago
Comments count
1
comments
Closed
10 years ago
Prefer conditional expressions to deferred initialization: missing mut.
Closed
10 years ago
Comments count
2