perlfunc: document return behavior of require and module_true feature

Author: Grinnz

.mailmap

@@ -232,6 +232,7 @@ Dagfinn Ilmari Mannsåker <[email protected]> Dagfinn Ilmari Mannsåker (via RT)
 Dagfinn Ilmari Mannsåker <[email protected]> [email protected] <[email protected]>
 Damian Conway <[email protected]> Damian Conway <[email protected]>
 Dan Book <[email protected]> Dan <[email protected]>
+Dan Book <[email protected]> Grinnz <[email protected]>
 Dan Dascalescu <[email protected]> Dan Dascalescu <[email protected]>
 Dan Faigin <unknown> Dan Faigin, Doug Landauer <unknown@longtimeago>
 Dan Jacobson <[email protected]> Dan Jacobson <[email protected]>

pod/perlfunc.pod

@@ -7111,6 +7111,7 @@ would have semantics similar to the following:
                 croak $@ ? "$@Compilation failed in require"
                          : "Can't locate $filename: $!\n";
             }
+            return 1 if $feature_module_true_enabled_in_file;
             if (!$result) {
                 delete $INC{$filename};
                 croak "$filename did not return true value";
@@ -7136,6 +7137,11 @@ affects the compilation unit within which the feature is used, and using
 it before requiring a module will not change the behavior of existing
 modules that do not themselves also use it.
 
+In this usage, the (truthy) result of the required file will be returned,
+but this should not be relied upon as it will not be returned in subsequent
+C<require> calls on the same file or with the 'module_true' feature enabled.
+To run a file and retrieve its return value, use L<C<do>|/do EXPR>.
+
 If EXPR is a bareword, C<require> assumes a F<.pm>
 extension and replaces C<::> with C</> in the filename for you,
 to make it easy to load standard modules.  This form of loading of