Changes

Jump to: navigation, search

Oxidation

308 bytes added, 23:36, 20 December 2017
Documentation
In general, erring on the side of tighter coupling is advisable. For example, the <tt>heapsize</tt> crate used in memory reporting was moved to crates.io, and then other crates came to depend on it. Later on it needed major API changes, and we ended up replacing it with a new crate called <tt>malloc_size_of</tt> (stored in Servo's repository) because that was easier than modifying <tt>heapsize</tt>.
= Documentation and assistance =
== Rust in general ==
* The [https://www.rust-lang.org/en-US/documentation.html Rust Documentation] page is the best place to start. In particular, the [https://doc.rust-lang.org/book/ The Rust Programming Language] provides a good overview.
* [https://www.rust-lang.org/en-US/community.html The Rust Community] page lists IRC channels, forums, and other places where Rust assistance can be obtained.
 
* [http://shop.oreilly.com/product/0636920040385.do Programming Rust: Fast, Safe Systems Development], by Jim Blandy & Jason Orendorff, is a detailed guide to the language.
* [https://github.com/ctjhoa/rust-learning rust-learning] is a huge collection of assorted Rust resources.
* [https://public.etherpad-mozilla.org/p/stylo Stylo workflow] (applies to any changes that straddle Gecko and Servo)
* The #servo IRC channel contains lots of people who know about both Rust and Gecko.
* Are you new to Rust and not sure if your Rust code could be improved? The following people can review Rust patches from an "is this good Rust code?" point of view.
** Alexis Beingessner
** Josh Bowman-Matthews
** Emilio Cobos Alvarez
** Manish Goregaokar
** Nika Layzell
** Cameron McCormack
= Supported Rust versions for Firefox builds =
Confirm
1,345
edits

Navigation menu