Word wrap for the playground

macros/macros1.rs

@@ -58,5 +58,6 @@ fn main() {
 
 
 
-// When you call a macro, you need to add something special compared to a regular function call. If
-// you're stuck, take a look at what's inside `my_macro`.
+// When you call a macro, you need to add something special compared to a
+// regular function call. If you're stuck, take a look at what's inside
+// `my_macro`.

macros/macros2.rs

@@ -58,8 +58,8 @@ macro_rules! my_macro {
 
 
 
-// Macros don't quite play by the same rules as the rest of Rust, in terms of what's available
-// where.
+// Macros don't quite play by the same rules as the rest of Rust, in terms of
+// what's available where.
 
 
 
@@ -68,5 +68,5 @@ macro_rules! my_macro {
 
 
 
-// Unlike other things in Rust, the order of "where you define a macro" versus "where you use it"
-// actually matters.
+// Unlike other things in Rust, the order of "where you define a macro" versus
+// "where you use it" actually matters.

macros/macros3.rs

@@ -60,8 +60,8 @@ fn main() {
 
 
 
-// In order to use a macro outside of its module, you need to do something special to the module to
-// lift the macro out into its parent.
+// In order to use a macro outside of its module, you need to do something
+// special to the module to lift the macro out into its parent.
 
 
 
@@ -70,5 +70,5 @@ fn main() {
 
 
 
-// The same trick also works on "extern crate" statements for crates that have exported macros, if
-// you've seen any of those around.
+// The same trick also works on "extern crate" statements for crates that have
+// exported macros, if you've seen any of those around.

macros/macros4.rs

@@ -72,5 +72,5 @@ fn main() {
 
 
 
-// The way macros are written, it wants to see something between each "macro arm", so it can
-// separate them.
+// The way macros are written, it wants to see something between each
+// "macro arm", so it can separate them.