Moved test to right place closes #1934

Author: JJ

doc/Language/5to6-perlfunc.pod6

@@ -2080,9 +2080,7 @@ As with C<wait>, the disposition of this is unclear.
 
 =item wantarray
 
-There is no C<wantarray> in Perl 6, because L<reasons|/language/faq#Why_is_wantarray_or_want_gone?_Can_I_return_different_things_in_different_contexts?>.
-
-There are very easy ways to cover many of the use cases which wantarray filled.
+There is no C<wantarray> in Perl 6; however, there are very easy ways to cover many of the use cases which wantarray filled.
 
 First, since Perl 6 does not need special reference syntax to contain
 a C<List> or C<Array> in a C<Scalar>, simply returning a list may be

doc/Language/faq.pod6

@@ -623,38 +623,6 @@ as an ordinary object, or ignore it in sink context.
 A C<Failure> returns C<False> from a C<defined> check, and you can extract
 the exception with the C<exception> method.
 
-=head2 Why is C<wantarray> or C<want> gone?
-Can I return different things in different contexts?
-
-Perl 5 has the L<C<wantarray>|/language/5to6-perlfunc#wantarray> function that
-tells you whether it's called in void, scalar or list context. Perl 6 has no
-equivalent construct because context does not flow inwards; i.e.,
-a routine would need time travel to know which context it's called in because
-context is lazy (known only when the results are used later).
-
-For example, Perl 6 has multiple dispatch. So, in a code example like
-
-    =begin code :preamble<sub f {}>
-    multi w(Int $x) { say 'Int' }
-    multi w(Str $x) { say 'Str' }
-    w(f());
-    =end code
-
-there's no way to determine if the caller of sub C<f> wants a string or
-an integer, because it's not yet known what the caller is. In general
-this requires solving the halting problem, which even Perl 6 compiler
-writers have trouble with.
-
-One way to achieve context sensitivity in Perl 6 is to return an object
-that knows how to respond to method calls that are typical for a context.
-In Perl 6, this is actually a L<lot easier|/language/5to6-perlfunc#wantarray>
-than it may sound, and other features of the language either mitigate the
-need to do so in the first place or make it possible to cover most of the
-use cases of wantarray.
-
-For example, regex matches return L<Match objects that know how to respond
-to list indexing, hash indexing, and that can turn into the matched
-string|/type/Match>.
 
 =head2 What's the difference between C<Pointer> and C<OpaquePointer>?