Feature #5444
closedObject.free
Description
I came across this gem today:
http://github.com/banister/free
Which led me to wonder if it might not be good to have this feature built-in to the core language. While not useful in most cases, it could be very useful to power-users who need to eek out every bit performance they can.
Updated by matz (Yukihiro Matsumoto) almost 13 years ago
- Status changed from Open to Rejected
While it might be considered useful from some brave power users, we are not going to add such unsafe features to the core.
Use the gem.
matz.
Updated by nobu (Nobuyoshi Nakada) almost 13 years ago
And, of course, the gem is not guaranteed across revisions.
Updated by Anonymous almost 13 years ago
help
Best,
Eric Scrivner,
Level2 Designs
On Oct 13, 2011, at 8:28 AM, Thomas Sawyer wrote:
Issue #5444 has been reported by Thomas Sawyer.
Feature #5444: Object.free
http://redmine.ruby-lang.org/issues/5444
Author: Thomas Sawyer
Status: Open
Priority: Normal
Assignee:
Category:
Target version: 1.9.x
I came across this gem today:
http://github.com/banister/free
Which led me to wonder if it might not be good to have this feature built-in to the core language. While not useful in most cases, it could be very useful to power-users who need to eek out every bit performance they can.