Log Message:
Update to 2.2001
Update DEPENDS

Upstream changes:
2.2001   2017-01-29

  [TESTS]

  - fixed variable interpolation in filename in test (RT#120033)

2.2000   2017-01-29

  [OTHER]

  - increased minimum required version of Sub::Name.

2.1905   2017-01-07 (TRIAL RELEASE)

  [ENHANCEMENTS]

  - Added support for __no_BUILD__ as a constructor argument to skip calling
    any BUILD subs (used internally by modules like Moo that have their own
    implementation of calling BUILD) (PR#142, Graham Knop)

2.1904   2016-12-22 (TRIAL RELEASE)

  [BUG FIXES]

  - Slight tweaks to the syntax used for hashes in a few tests, that were
    broken by a recent Test::More release that started using a new namespace
    that clashes with a (bareword) type name in these tests. (PR#141,
    D.Maestro)

2.1903   2016-11-22 (TRIAL RELEASE)

  [ENHANCEMENTS]

  - When an attribute defines two methods (say a reader and writer) with the
    same name, this now generates a warning.

  - The warning when attribute methods overwrite one another is now much more
    informative. It includes the type of accessors involve (reader, writer,
    predicate, etc.) as well as the file and line where each accessor was
    defined. Fixes RT #118325.

  [BUG FIXES]

  - Brought back the Moose::Meta::Method::Delegation->_get_delegate_accessor
    method for the benefit of MooseX::CurriedDelegation.

  - The definition context (package, file, & line) for attributes on
    Class::MOP and Moose metaclasses was wrong in all cases.

2.1902   2016-10-23 (TRIAL RELEASE)

  [ENHANCEMENTS]

  - The stack trace for an inlined delegation now tells you where the
    delegating attribute was declared (file and line number).

2.1901   2016-10-20 (TRIAL RELEASE)

  [TESTS]

  - warnings are only checked for in tests under AUTHOR_TESTING, so as to not
    prevent installation when warnings occur in prerequisites.

2.1900   2016-10-09 (TRIAL RELEASE)

  [ENHANCEMENTS]

  - Most delegations are inlined now. This is not done for speed but rather to
    improve stack traces when the delegated-to method throws an exception or
    when the delegated-to method simply does not exist in the
    delegatee. Previously, this stack trace and associated error were less
    helpful than they could have been. Requested by Tim Bunce, Olaf Alders,
    and Van de Bugger. (RT#46614, RT#98402, and RT#109631).