bdurand (Brian Durand)
- Login: bdurand
- Email: brian@embellishedvisions.com
- Registered on: 12/18/2010
- Last sign in: 10/04/2011
Issues
| open | closed | Total | |
|---|---|---|---|
| Assigned issues | 0 | 0 | 0 |
| Reported issues | 0 | 1 | 1 |
Activity
01/14/2011
-
03:40 AM Ruby Feature #4168: WeakRef is unsafe to use in Ruby 1.9
- =begin
Ruby reference queue implementation:
http://github.com/bdurand/ref/blob/master/lib/ref/reference_queue.rb
=end
-
- =begin
Charles: The logic to enqueue a weak reference onto a reference queue needs to happen at some point in the garbage collection cycle and something needs to keep track of which weak references need to be enqueued on which queues. M...
01/13/2011
-
- =begin
My 2 cents on reference queues is that they aren't critical to Ruby weak references because of the way Ruby allows finalizers to be defined for objects external to the objects class definition. A ruby implementation of a weak key...
01/11/2011
-
- =begin
After further review, I found the synchronization issue is definitely with Rubinius and that not synchronizing breaks on other Rubies where hash operations are not atomic. Reverted patch files attached.
=end
01/06/2011
-
- =begin
I found what may be a bug in my patch. When testing similar code on Rubinius, I found the process deadlocking. I believe what was happening is that a thread was stopped in order to run garbage collection when it was inside a sync...
12/18/2010
-
- =begin
Rdoc comments on the WeakReference class didn't get synced with the code. Updated file attached that just fixes the comments.
=end
-
- =begin
I've found a couple issues with the implementation of WeakRef in Ruby 1.9.
1. WeakRef is unsafe to use because the ObjectSpace will recycle object ids for use with newly allocated objects after the old objects have been gar...