Update to 0.18
- New upstream release 0.18 - Using coercions with positional parameters could cause a "Modification of a read-only value attempted" exception when the generated code tried to assign to elements of @_; this is now fixed by making a copy if any of the types have a coercion - Using Moose types with coercions in a positional params check would cause invalid code to be generated; this could also happen with Type::Tiny if either the type or a coercion could not be inlined
This commit is contained in:
parent
38c6162026
commit
5b75ebeaef
|
@ -1,5 +1,5 @@
|
|||
Name: perl-Params-ValidationCompiler
|
||||
Version: 0.17
|
||||
Version: 0.18
|
||||
Release: 1%{?dist}
|
||||
Summary: Build an optimized subroutine parameter validator once, use it forever
|
||||
License: Artistic 2.0
|
||||
|
@ -74,6 +74,16 @@ make test
|
|||
%{_mandir}/man3/Params::ValidationCompiler::Exceptions.3*
|
||||
|
||||
%changelog
|
||||
* Mon Nov 14 2016 Paul Howarth <paul@city-fan.org> - 0.18-1
|
||||
- Update to 0.18
|
||||
- Using coercions with positional parameters could cause a "Modification of a
|
||||
read-only value attempted" exception when the generated code tried to
|
||||
assign to elements of @_; this is now fixed by making a copy if any of the
|
||||
types have a coercion
|
||||
- Using Moose types with coercions in a positional params check would cause
|
||||
invalid code to be generated; this could also happen with Type::Tiny if
|
||||
either the type or a coercion could not be inlined
|
||||
|
||||
* Mon Nov 7 2016 Paul Howarth <paul@city-fan.org> - 0.17-1
|
||||
- Update to 0.17
|
||||
- When using positional parameters, parameters with a default are now
|
||||
|
|
Loading…
Reference in New Issue