Finally, triggers are called whenever the value of the attribute is changed by
a Native delegation.
-These changes are only likely to break code in a few cases. If you have a
-typed arrayref or hashref attribute where the type enforces a constraint on
-the whole collection, this constraint will now be checked. It's possible that
-code which previously ran without errors will now cause the constraint to
-fail. However, presumably this is a good thing ;)
+These changes are only likely to break code in a few cases.
+
+The inlning code may or may not preserve the original reference when changes
+are made. In some cases, methods which change the value may replace it
+entirely. This will break tied values.
+
+If you have a typed arrayref or hashref attribute where the type enforces a
+constraint on the whole collection, this constraint will now be checked. It's
+possible that code which previously ran without errors will now cause the
+constraint to fail. However, presumably this is a good thing ;)
If you are passing invalid arguments to a delegation which were previously
-being ignore, these will now fail.
+being ignore, these calls will now fail.
-The other issue is the use of a trigger. If your code relied on the trigger
-only being called for a regular writer, that may cause problems.
+If your code relied on the trigger only being called for a regular writer,
+that may cause problems.
As always, you are encouraged to test before deploying the latest version of
Moose to production.