Thanks to nothingmuch for assistance in the explanations. --- lib/Moose/Manual/BestPractices.pod | 7 +++++-- 1 files changed, 5 insertions(+), 2 deletions(-)
diff --git a/lib/Moose/Manual/BestPractices.pod b/lib/Moose/Manual/BestPractices.pod index 30c5673..9349718 100644 --- a/lib/Moose/Manual/BestPractices.pod +++ b/lib/Moose/Manual/BestPractices.pod @@ -32,8 +32,11 @@ Moose sugar and making your class immutable. 1; -The C<no Moose> bit is simply good code hygiene, and making classes -immutable speeds up a lot of things, most notably object construction. +The C<no Moose> bit simply good code hygiene, as it removes all the +Moose keywords that are no longer needed once your class has been +built. C<make_immutable> relinquishes your right to make further +changes to your class, and allows Moose to speed up a lot of things, +most notably object construction. =head2 Never override C<new> -- 1.6.1.2
