Re^2: Creating accessors on the fly, or not...

[dsheroh]

Can you point me to a good explanation of why make_immutable is recommended?

Going through the first 50 google results for "perl moose make_immutable", I came across a few statements that "make_immutable is a Moose best practice", but none of them stated the reason for it. Is this solely because it makes object creation faster (as shown by Pichi's Moose benchmarks) or are there other reasons aside from performance?

[stvn]

Can you point me to a good explanation of why make_immutable is recommended?

So in an effort to contribute to the Iron Man blogging challenge I have posted a response here. I will copy the "short answer" part of my post here, but for a more detailed and in-depth explanation check out the blog post.

So the short answer is that making your class immutable is good because it memoizes several metaclass methods and installs an optimized constructor and destructor for your class and therefore helps reduce a fair amount of the cost (during runtime) of all the abstraction that the MOP provides.

[dsheroh]

Thanks for the very thorough answer! It really clarifies why, in Pichi's benchmarks, the immutable version creates objects about 10x faster than the mutable one. (And I'm always happy to provide someone with an excuse for an Iron Man post, seeing as I always seem to be looking for them myself.)