Skip to content

Commit

Permalink
no preposition needed with 'trust'
Browse files Browse the repository at this point in the history
  • Loading branch information
coke committed Feb 11, 2019
1 parent 6126c6c commit 1993a30
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
2 changes: 1 addition & 1 deletion doc/Language/traps.pod6
Expand Up @@ -748,7 +748,7 @@ my $set = <a b c>.Set;
# OUTPUT: «c => True␤b => True␤a => True␤»
=end code
Every iteration might (and will) yield a different order, so you cannot trust on
Every iteration might (and will) yield a different order, so you cannot trust
a particular sequence of the elements of a set. If order does not matter, just
use them that way. If it does, use C<sort>
Expand Down
2 changes: 1 addition & 1 deletion doc/Type/Mu.pod6
Expand Up @@ -441,7 +441,7 @@ In non-sink context, C<say> will always return C<True>.
say (1,[1,2],"foo",Mu).map: so *.say ;
# OUTPUT: «1␤[1 2]␤foo␤(Mu)␤(True True True True)␤»
However, this behavior is just conventional and you shouldn't trust on it for
However, this behavior is just conventional and you shouldn't trust it for
your code. It's useful, however, to explain certain behaviors.
C<say> is first printing out in C<*.say>, but the outermost C<say> is printing
Expand Down

0 comments on commit 1993a30

Please sign in to comment.