From 4217af78d8305d4e679e9f6490e7bcb1e902ceab Mon Sep 17 00:00:00 2001 From: Alexander <39702500+threadless-screw@users.noreply.github.com> Date: Wed, 26 Sep 2018 09:42:26 +0200 Subject: [PATCH] Fixed bad URL (#2333) --- doc/Type/Signature.pod6 | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/Type/Signature.pod6 b/doc/Type/Signature.pod6 index bf1ba235d..6a5641495 100644 --- a/doc/Type/Signature.pod6 +++ b/doc/Type/Signature.pod6 @@ -395,18 +395,18 @@ be confusing, since the terms have subtly different meanings. As explained above, I is concerned with the distinction between type objects and object instances. A type object is always indefinite, while an -object instance is always definite. Whether or not an object is a type +object instance is always definite. Whether an object is a type object/indefinite or an object instance/definite can be verified using the L (meta)method. I should be distinghuished from I, which is concerned with the difference between defined and undefined objects. Whether an object is -defined or undefined can be verified using the C<.defined>-method, which is +defined or undefined can be verified using the C-method, which is implemented in class L. By default a type object is considered undefined, while an object instance is considered defined; that is: C<.defined> returns C on a type object, and C otherwise. But this default behaviour may be overridden by subclasses. An example of a subclass that -overrides the default C<.defined> behaviour is L, +overrides the default C<.defined> behaviour is L, so that even an instantiated C acts as an undefined value: my $a = Failure; # Initialize with type object