Don't skip if not needed.

Drop back to :solo testing when needed, remove the skip
entirely when possible.
We're not executing any of this code, only compiling it.

Author: coke

doc/Language/contexts.pod6

@@ -125,7 +125,7 @@ string context will behave as a string, thus yielding an error.
 
 However,
 
-=begin code :skip-test<Stringification error>
+=begin code
 my $non-empty = Buf.new(0x3, 0x33);
 my $empty = [];
 my $non-empty-also = Buf.new(0x2,0x22);
@@ -158,4 +158,4 @@ contextualizer, with the result shown above.
 
 =end pod
 
-# vim: expandtab softtabstop=4 shiftwidth=4 ft=perl6
+# vim: expandtab softtabstop=4 shiftwidth=4 ft=perl6

doc/Language/grammar_tutorial.pod6

@@ -336,7 +336,7 @@ values: create, retrieve, update or delete.
 There are several ways to accomplish this. For example, you could change the
 command method:
 
-    =begin code :skip-test
+    =begin code :solo
     token command { \w+ }
 
     # …becomes…
@@ -715,4 +715,4 @@ tokens.
 
 =end pod
 
-# vim: expandtab softtabstop=4 shiftwidth=4 ft=perl6
+# vim: expandtab softtabstop=4 shiftwidth=4 ft=perl6

doc/Language/hashmap.pod6

@@ -166,7 +166,7 @@ However, what you are defining here is a key pointing to a L<Pair>, which is
 fine if that is what you want, and if your nested hash has got a single key. But
 C<%h<e>> will point to a C<Pair> which will have these consequences:
 
-=begin code :skip-test<Illustrates an error>
+=begin code
 my %h =  e => f => 'g';
 %h<e><q> = 'k';
 # OUTPUT: «(exit code 1) Pair␤Cannot modify an immutable Str (Nil)␤  in block <unit>»

doc/Language/io-guide.pod6

@@ -251,7 +251,7 @@ my $data = 'foo/bar'.IO.add($file).slurp;
 However, it's fine to use it for things not otherwise provided by L<IO::Path>.
 For example, the L<C«.devnull» method|/routine/devnull>:
 
-=for code :skip-test
+=for code
 {
     temp $*OUT = open :w, $*SPEC.devnull;
     say "In space no one can hear you scream!";

doc/Language/list.pod6

@@ -613,7 +613,7 @@ via the C<shape> method.
 
 Shape will control the amount of elements that can be assigned by dimension:
 
-=begin code :skip-test<Illustrates exception>
+=begin code
 my @just-two[2] = <alpha betta kappa>;
 # Will throw exception: «Index 2 for dimension 1 out of range (must be 0..1)»
 =end code
@@ -749,4 +749,4 @@ creature should never be passed back to unsuspecting users.
 
 =end pod
 
-# vim: expandtab softtabstop=4 shiftwidth=4 ft=perl6
+# vim: expandtab softtabstop=4 shiftwidth=4 ft=perl6

doc/Language/math.pod6

@@ -325,7 +325,7 @@ We declare the derivatives that are in our model. In this case, if
 you remember our equation, we have our variable I<x> and its derivative
 I<x'> (usually know as the velocity).
 
-=begin code :skip-test<Snippet for explanation purposes>
+=begin code
 derivatives => {
     velocity     => 'x',
     },
@@ -338,7 +338,7 @@ formulas for the derivatives that are not also integration variables
 (in this case, only I<x>), and for other variables we use in the formulas
  (the growth rate).
 
-=begin code :skip-test<Snippet for explanation purposes>
+=begin code
 variables   => {
     velocity           => { $:growth_constant * $:x},
     growth_constant    => { 1 },   # basal growth rate
@@ -352,7 +352,7 @@ Finally we declare our initial conditions and use I<captures> to
 tell L<C<Math::Model>|https://github.com/moritz/Math-Model> which
 variable or variables to record while the simulation is running.
 
-=begin code :skip-test<Snippet for explanation purposes>
+=begin code
 initials    => {
     x       => 3,
 },

doc/Language/module-packages.pod6

@@ -122,7 +122,7 @@ with the C<unit> keyword; C<unit module> specifies that the
 rest of the compilation unit is part of the declared module. Here's
 C<Foo.pm6> rewritten with C<unit>:
 
-=begin code :skip-test<filesystem related>
+=begin code :solo
 unit module Foo;
 
 sub greeting ($name = 'Camelia') { "Greetings, $name!" }

doc/Language/modules.pod6

@@ -491,7 +491,7 @@ Be careful I<not> to put C<sub EXPORT> after L«C<unit> declarator|/syntax/unit
 If you do so, it'll become just a sub inside your package, rather than the special
 export sub:
 
-=for code :skip-test<bad example>
+=for code :solo
     unit module Bar;
     sub EXPORT { %(Foo => &say) } # WRONG!!! Sub is scoped wrong
 

doc/Language/nativecall.pod6

@@ -41,7 +41,7 @@ are trying to create.
 NativeCall provides a C<symbol> trait for you to specify the name of the native
 routine in your library that may be different from your Perl subroutine name.
 
-=begin code :skip-test
+=begin code :solo
 unit module Foo;
 use NativeCall;
 our sub init() is native('foo') is symbol('FOO_INIT') { * }
@@ -667,7 +667,7 @@ to be prepended with "lib" and appended with ".so" (or just appended with
 ".dll" on Windows), and will be searched for in the paths in the
 LD_LIBRARY_PATH (PATH on Windows) environment variable.
 
-=begin code :skip-test
+=begin code
     use NativeCall;
     constant LIBMYSQL = 'mysqlclient';
     constant LIBFOO = '/usr/lib/libfoo.so.1';
@@ -986,7 +986,7 @@ a buffer with the C<addrinfo>.
 
 Putting all these together, leads to the following program:
 
-=begin code :skip-test<Code works as is. Error with compilation maybe related to wrapping>
+=begin code :solo
 #!/usr/bin/env perl6
 
 use v6;

doc/Language/nativetypes.pod6

@@ -154,7 +154,7 @@ my Pointer[void] $native = nativecast(Pointer[void], Blob.new(0x22, 0x33));
 However, outside that, the functionality it offers is quite limited, since
 pointers to void cannot be dereferenced:
 
-=begin code :skip-test<unhandled type error>
+=begin code
 use NativeCall;
 my Pointer[void] $native = nativecast(Pointer[void], Buf.new(0x22, 0x33));
 say $native.deref; # ERROR OUTPUT: «Internal error: unhandled target type␤»