v6 -> v6.c

doc/Language/5to6-nutshell.pod6

@@ -1327,7 +1327,7 @@ Synopsis 11, however it works.)
 
 The module C<Bar> now is merely a file called C<Bar.pm> with the following contents:
 
-    use v6;
+    use v6.c;
 
     sub EXPORT(*@import-list) {
         my %exportable-subs =

doc/Language/faq.pod6

@@ -683,7 +683,7 @@ Try it on your system. You may be pleasantly surprised!
 Examples:
 
     # Perl 6 version
-    use v6;
+    use v6.c;
 
     class Foo { has $.i is rw };
 

doc/Language/glossary.pod6

@@ -546,7 +546,7 @@ X<|Mainline>
 
 The C<mainline> is the program text that is not part of any kind of block.
 
-    use v6;     # mainline
+    use v6.c;     # mainline
     sub f {
                 # not in mainline, in sub f
     }

doc/Language/grammars.pod6

@@ -280,7 +280,7 @@ argument. If no such method exists, it is skipped.
 Here is a contrived example of a grammar and actions in action:
 
 =begin code
-use v6;
+use v6.c;
 
 grammar TestGrammar {
     token TOP { \d+ }
@@ -312,7 +312,7 @@ for C<< $/<capture> >>).
 A slightly more involved example follows:
 
 =begin code
-use v6;
+use v6.c;
 
 grammar KeyValuePairs {
     token TOP {

doc/Language/objects.pod6

@@ -827,7 +827,7 @@ $t.visit-postorder(&say);   # 4 \n 6 \n 5
 Here the signature consists only of a type capture, but any signature will do:
 
 =begin code
-use v6;
+use v6.c;
 
 enum Severity <debug info warn error critical>;
 

doc/Language/testing.pod6

@@ -119,7 +119,7 @@ project's base directory.
 
 A typical test file looks something like this:
 
-    use v6;
+    use v6.c;
     use Test;      # a Standard module included with Rakudo
     use lib 'lib';
 
@@ -129,7 +129,7 @@ A typical test file looks something like this:
 
     done-testing;  # optional with 'plan'
 
-We ensure that we're using Perl 6, via the C<use v6> pragma, then we load
+We ensure that we're using Perl 6, via the C<use v6.c> pragma, then we load
 the C<Test> module and specify where our libraries are.  We then specify how
 many tests we I<plan> to run (such that the testing framework can tell us if
 more or fewer tests were run than we expected) and when finished with the
@@ -367,7 +367,7 @@ check for equality of (deep) data structures. The function accepts an optional
 C<$description> of the test.
 
 =begin code
-use v6;
+use v6.c;
 use Test;
 plan 1;
 

doc/Language/traps.pod6

@@ -28,7 +28,7 @@ case.
 
 For example
 
-    use v6;
+    use v6.c;
     class Point {
         has $.x;
         has $.y;
@@ -67,7 +67,7 @@ which operates on the attributes directly.
 When you define your own C<BUILD> submethod, you must take care of
 initializing all attributes yourself. For example
 
-    use v6;
+    use v6.c;
     class A {
         has $.x;
         has $.y;
@@ -97,7 +97,7 @@ which can be shortened to:
 Another, more general approach is to leave C<BUILD> alone, and hook into the
 C<BUILDALL> mechanism instead:
 
-    use v6;
+    use v6.c;
     class A {
         has $.x;
         has $.y;

doc/Type/DateTime.pod6

@@ -19,7 +19,7 @@ Time zones are handled as L<Integers|/type/Int> in B<seconds> offset from UTC,
 not by time zone name.
 
 =begin code
-use v6;
+use v6.c;
 my $dt = DateTime.new(
     year    => 2015,
     month   => 11,

doc/Type/IO/ArgFiles.pod6

@@ -13,15 +13,15 @@ standard input.
 One could print the lines of the files specified on the command line to
 standard output using code such as this:
 
-    use v6;
+    use v6.c;
 
     my $argfiles = IO::ArgFiles.new(args => @*ARGS);
 
     .say for $argfiles.lines;
 
 Or equivalently by using the C<eof> and C<get> methods:
 
-    use v6;
+    use v6.c;
 
     my $argfiles = IO::ArgFiles.new(args => @*ARGS);
 
@@ -31,7 +31,7 @@ Or equivalently by using the C<eof> and C<get> methods:
 
 Here's the same thing via the C<slurp> method:
 
-    use v6;
+    use v6.c;
 
     my $argfiles = IO::ArgFiles.new(args => @*ARGS);
 
@@ -45,7 +45,7 @@ This class is the magic behind the C<$*ARGFILES> variable.  This variable
 provides a way to iterate over files passed in to the program on the command
 line.  Thus the examples above can be simplified like so:
 
-    use v6;
+    use v6.c;
 
     .say for $*ARGFILES.lines;
 

doc/Type/IO/Socket/Async.pod6

@@ -13,7 +13,7 @@ Here is the equivalent example to that in L<IO::Socket::INET> of a simple
 echo server that listens on port 3333:
 
 =begin code :skip-test
-use v6;
+use v6.c;
 
 react {
     whenever IO::Socket::Async.listen('localhost', 3333) -> $conn {
@@ -27,7 +27,7 @@ react {
 And a client that connects to it, and prints out what the server answers:
 
 =begin code :skip-test
-use v6;
+use v6.c;
 
 await IO::Socket::Async.connect('localhost', 3333).then( -> $p {
     if $p.status {

doc/Type/IO/Socket/INET.pod6

@@ -12,7 +12,7 @@ Here is an example of a very simplistic "echo" server that listens on
 localhost, port 3333:
 
 =begin code :skip-test
-use v6;
+use v6.c;
 
 my $listen = IO::Socket::INET.new(:listen, :localhost<localhost>, :localport(3333));
 loop {
@@ -27,7 +27,7 @@ loop {
 And a client that connects to it, and prints out what the server answers:
 
 =begin code :skip-test
-use v6;
+use v6.c;
 
 my $conn = IO::Socket::INET.new(:host<localhost>, :port(3333));
 $conn.print: 'Hello, Perl 6';

doc/Type/Proc/Async.pod6

@@ -38,7 +38,7 @@ Done.
 
 An example that opens an external program for writing:
 
-    use v6;
+    use v6.c;
     my $prog = Proc::Async.new(:w, 'hexdump', '-C');
     my $promise = $prog.start;
     await $prog.write(Buf.new(12, 42));

doc/Type/Thread.pod6

@@ -17,7 +17,7 @@ primitives, like L<start|/type/Promise#method start>, which also runs in
 parallel and returns a L<Promise|/type/Promise>.
 
 =begin code
-use v6;
+use v6.c;
 my @threads = (^10).map: {
     Thread.start(
         name => "Sleepsorter $_",