From c78fb9236ddbd8feeea18848706315d7e2d3d04b Mon Sep 17 00:00:00 2001 From: kud1ing Date: Tue, 13 May 2014 13:23:52 -0700 Subject: [PATCH] format --- Note-style-guide.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Note-style-guide.md b/Note-style-guide.md index 330145b..2bb65a2 100644 --- a/Note-style-guide.md +++ b/Note-style-guide.md @@ -20,7 +20,7 @@ Here are some rough guidelines to Rust style. They are followed unevenly and the * Constructors should be methods called `new` or `new_with_more_details`. * Constructors that simply convert from another type should be methods called `from_foo`. * When writing a binding to an external library, put the raw C bindings in a module called `ffi` (rather than `ll`). Do not create high-level bindings called `hl`. -* lifetime names should be lowercase and are often simply 'a +* lifetime names should be lowercase and are often simply `'a`. ## Trait naming @@ -235,4 +235,4 @@ A ```for``` loop is always preferable to a ```while``` loop unless the loop coun # Questions and TODO * Do we want to prefer 'top-down' organization? -* Prefer unsafe pointers to unsafely transmuting borrowed pointers +* Prefer unsafe pointers to unsafely transmuting borrowed pointers \ No newline at end of file