Skip to content

Commit

Permalink
Fix broken links
Browse files Browse the repository at this point in the history
  • Loading branch information
dmc00 committed Dec 25, 2017
1 parent ac31bd4 commit 8965814
Show file tree
Hide file tree
Showing 2 changed files with 6 additions and 2 deletions.
3 changes: 3 additions & 0 deletions CREDITS
Expand Up @@ -86,6 +86,9 @@ E: davidnmfarrell@gmail.com
N: David H. Adler
E: dha@pobox.com

N: David M. Cawthon
E: dmc00@fastmail.com

N: Dmitriy Olshevskiy
E: olshevskiy87@bk.ru

Expand Down
5 changes: 3 additions & 2 deletions doc/Language/setbagmix.pod6
Expand Up @@ -79,15 +79,16 @@ one C<Set> is a subset of another C<Set>.
These infixes can be written using the UTF-8 character that represents the
function (like L<∈|/routine/∈>, or L<∪|/routine/∪>), or they can be written with an
equivalent ASCII version (like L<(elem)|/routine/(elem)> or L<(|)|/routine/(|)>).
equivalent ASCII version (like L<(elem)|/routine/(elem)> or L<(E<VERTICAL
LINE>)|/routine/(|)>).
Most of the time, explicitly using C<Set> objects with these infixes is
unnecessary. All of the infix operators will work on any objects of type
L<Any|/type/Any> for its arguments (e.g., L<List|/type/List>,
L<Array|/type/Array>, L<Mix|/type/Mix>, etc.) and coerce them to C<Set>
where needed.
In some cases, if the type of an argument is a L<Bag/type/Bag>, the infix
In some cases, if the type of an argument is a L<Bag|/type/Bag>, the infix
operator will behave in a different but analogous way to the way it would
behave with only C<Set> arguments.
Expand Down

0 comments on commit 8965814

Please sign in to comment.