Skip to content
Browse files
Add dividers between the guidelines to make it easier to read
  • Loading branch information
repi committed Jun 12, 2019
1 parent 07c2b04 commit db94f53e88de93290104dcabfcbd6d8b51b4d36b
Showing 1 changed file with 8 additions and 0 deletions.
@@ -8,12 +8,16 @@ Guidelines and recommendations we use at [Embark]( for devel

This is not meant to be an exhaustive collection and resource of all best practices in Rust, that is best covered by the [Rust Book]( and other references. Instead this is list of specific guidelines and recommendations that we've run into and want to highlight and standardize on within Embark.


### 001 - Run rustfmt on save

__Motivation:__ We want to keep a consistent code base where we don't have to argue about style, so we use rustfmt on everything and verify on CI that it has been run. So highly recommend everyone to configure their editor to run rustfmt on save as it is more error prone to run it before commit.

With VS Code this should be automatic for our repos, see [section](#visual-studio-code).


### 002 - Prefer synchronization primitives from [`parking_lot`]( instead of `std::sync`

__Motivation:__ The `parking_lot` implementations are smaller, faster, and avoids poisioning errors which makes them more ergonomic and easier to use.
@@ -36,6 +40,8 @@ let mutex = Mutex::new(1u32);

__Todo:__ Would be great to automatically verify this through something like a custom clippy lint, or even better: have the `parking_lot` primitives eventually find their way into std.


### 003 - Opt-in for Clippy and Rust 2018 style warnings for every crate

__Motivation:__ Keeps our code high quality and catches common errors and inefficiencies. We already verify on CI that clippy finds no warnings, and by opting in to warnings in every crate it also enables tools like RLS in VS Code to know that Clippy warnings
@@ -49,6 +55,8 @@ Add this to the top of the main file (`` or ``) for all of our crate

__Todo:__ Would be great if we could configure this globally for our workspace instead of for each crate (more error prone). [#22](


## Development environments

### Visual Studio Code

0 comments on commit db94f53

Please sign in to comment.