Moose::Meta::TypeConstraint::Registry - registry for type constraints


Moose documentation  | view source Contained in the Moose distribution.

Index


NAME

Top

Moose::Meta::TypeConstraint::Registry - registry for type constraints

VERSION

Top

version 2.0010

DESCRIPTION

Top

This class is a registry that maps type constraint names to Moose::Meta::TypeConstraint objects.

Currently, it is only used internally by Moose::Util::TypeConstraints, which creates a single global registry.

INHERITANCE

Top

Moose::Meta::TypeConstraint::Registry is a subclass of Class::MOP::Object.

METHODS

Top

Moose::Meta::TypeConstraint::Registry->new(%options)

This creates a new registry object based on the provided %options:

* parent_registry

This is an optional Moose::Meta::TypeConstraint::Registry object.

* type_constraints

This is hash reference of type names to type objects. This is optional. Constraints can be added to the registry after it is created.

$registry->get_parent_registry

Returns the registry's parent registry, if it has one.

$registry->has_parent_registry

Returns true if the registry has a parent.

$registry->set_parent_registry($registry)

Sets the parent registry.

$registry->get_type_constraint($type_name)

This returns the Moose::Meta::TypeConstraint object from the registry for the given name, if one exists.

$registry->has_type_constraint($type_name)

Returns true if the registry has a type of the given name.

$registry->add_type_constraint($type)

Adds a new Moose::Meta::TypeConstraint object to the registry.

$registry->find_type_constraint($type_name)

This method looks in the current registry for the named type. If the type is not found, then this method will look in the registry's parent, if it has one.

BUGS

Top

See BUGS in Moose for details on reporting bugs.

AUTHOR

Top

Stevan Little <stevan@iinteractive.com>

COPYRIGHT AND LICENSE

Top


Moose documentation  | view source Contained in the Moose distribution.