Some reflow in preparation for #1603

Author: JJ

doc/Language/traps.pod6

@@ -11,32 +11,34 @@ and discovery.
 
 This document aims to show common misconceptions in order to avoid them.
 
-During the making of Perl 6 great pains were taken to get rid of warts in
-the syntax.  When you whack one wart, though, sometimes another pops up.  So
-a lot of time was spent finding the minimum number of warts or trying to put
-them where they would rarely be seen.  Because of this, Perl 6's warts are
-in different places than you may expect them to be when coming from another
-language.
+During the making of Perl 6 great pains were taken to get rid of warts
+in the syntax.  When you whack one wart, though, sometimes another pops
+up.  So a lot of time was spent finding the minimum number of warts or
+trying to put them where they would rarely be seen.  Because of this,
+Perl 6's warts are in different places than you may expect them to be
+when coming from another language.
 
 =head1 Variables and constants
 
 =head2 Constants are computed at compile time
 
-Constants are computed at compile time, so if you use them in modules keep in mind
-that their values will be frozen due to pre-compilation of the module itself:
+Constants are computed at compile time, so if you use them in modules
+keep in mind that their values will be frozen due to pre-compilation of
+the module itself:
 
 =for code :skip-test
 # WRONG (most likely):
 unit module Something::Or::Other;
 constant $config-file = "config.txt".IO.slurp;
 
-The C<$config-file> will be slurped during pre-compilation and changes to
-C<config.txt> file won't be re-loaded when you start the script again; only when
-the module is re-compiled.
+The C<$config-file> will be slurped during pre-compilation and changes
+to C<config.txt> file won't be re-loaded when you start the script
+again; only when the module is re-compiled.
 
 Avoid L<using a container|/language/containers> and prefer
-L<binding a value|/language/containers#Binding> to a variable that offers
-a behaviour similar to a constant, but allowing the value to get updated:
+L<binding a value|/language/containers#Binding>
+to a variable that offers a
+behaviour similar to a constant, but allowing the value to get updated:
 
 =for code :skip-test
 # Good; file gets updated from 'config.txt' file on each script run:
@@ -45,7 +47,8 @@ my $config-file := "config.txt".IO.slurp;
 
 =head2 Assigning to C<Nil> produces a different value, usually C<Any>.
 
-Actually, assigning to C<Nil> L<reverts the variable to its default value|https://docs.perl6.org/type/Nil>. So:
+Actually, assigning to C<Nil>
+L<reverts the variable to its default value|https://docs.perl6.org/type/Nil>. So:
 
 =begin code
 my @a = 4, 8, 15, 16;
@@ -76,12 +79,14 @@ my $result2 = 'abcdef' ~~ / dex /;
 say "Result2 is { $result2.^name }"; # OUTPUT: «Result2 is Any␤»
 =end code
 
-A L<C<Match> will be C<Nil>|https://docs.perl6.org/language/regexes#Literals> if it finds nothing; however it assigning C<Nil> to C<$result2> above will result in its default value, which is C<Any> as shown.
+A L<C<Match> will be C<Nil>|https://docs.perl6.org/language/regexes#Literals>
+if it finds nothing; however it assigning C<Nil> to C<$result2> above
+will result in its default value, which is C<Any> as shown.
 
 =head2 Using a block to interpolate anon state vars
 
-The programmer intended for the code to count the number of times the routine
-is called, but the counter is not increasing:
+The programmer intended for the code to count the number of times the
+routine is called, but the counter is not increasing:
 
     =begin code
     sub count-it { say "Count is {$++}" }
@@ -94,7 +99,7 @@ is called, but the counter is not increasing:
     =end code
 
 When it comes to state variables, the block in which the vars are
-declared gets cloned — and vars get initialized anew—whenever that
+declared gets cloned —and vars get initialized anew— whenever that
 block's block is re-entered. This lets constructs like the one below
 behave appropriately: the state variable inside the loop gets
 initialized anew each time the sub is called:
@@ -151,8 +156,8 @@ Alternatively, you can also use the L<concatenation operator|/routine/~> instead
 
 =head2 Beware of empty "blocks"
 
-Curly braces are used to declare blocks. However, empty curly braces will
-declare a hash.
+Curly braces are used to declare blocks. However, empty curly braces
+will declare a hash.
 
 =begin code
 $ = {say 42;} # Block
@@ -161,7 +166,8 @@ $ = {…}       # Block
 $ = { }       # Hash
 =end code
 
-You can use the second form if you effectively want to declare an empty block:
+You can use the second form if you effectively want to declare an empty
+block:
 
     my &does-nothing = {;};
     say does-nothing(33);# OUTPUT: «Nil␤»
@@ -171,9 +177,9 @@ You can use the second form if you effectively want to declare an empty block:
 
 =head2 Assigning to attributes
 
-Newcomers often think that, because attributes with accessors are declared
-as C<has $.x>, they can assign to C<$.x> inside the class. That's not the
-case.
+Newcomers often think that, because attributes with accessors are
+declared as C<has $.x>, they can assign to C<$.x> inside the class.
+That's not the case.
 
 For example
 
@@ -229,8 +235,8 @@ class A {
 say A.new(x => 42).x;       # OUTPUT: «Any␤»
 =end code
 
-leaves C<$!x> uninitialized, because the custom C<BUILD> doesn't initialize
-it.
+leaves C<$!x> uninitialized, because the custom C<BUILD> doesn't
+initialize it.
 
 B<Note:> Consider using L<TWEAK|/language/objects#index-entry-TWEAK>
 instead. L<Rakudo|/language/glossary#Rakudo> supports L<TWEAK|/language/objects#index-entry-TWEAK> method