From: "miragliuolo1 (Joe Miragliuolo)" <sod@...>
Date: 2013-05-12T07:34:27+09:00
Subject: [ruby-core:54920] [ruby-trunk - Bug #8392][Open] stdlib's 'forwardable' documentation has a bad example


Issue #8392 has been reported by miragliuolo1 (Joe Miragliuolo).

----------------------------------------
Bug #8392: stdlib's 'forwardable' documentation has a bad example
https://bugs.ruby-lang.org/issues/8392

Author: miragliuolo1 (Joe Miragliuolo)
Status: Open
Priority: Normal
Assignee: 
Category: 
Target version: 
ruby -v: ruby 2.0.0p0 (2013-02-24 revision 39474) [x86_64-darwin11.4.2]
Backport: 1.9.3: UNKNOWN, 2.0.0: UNKNOWN


=begin
As this is a problem with the documentation, there are no steps required to reproduce it.
My Ruby version is currently ruby 2.0.0p0 (2013-02-24 revision 39474) [x86_64-darwin11.4.2], but this documentation problem appears to have been in Ruby since at least ruby 1.9.3p194 (2012-04-20 revision 35410) [x86_64-darwin11.4.0].

Problem:
The second example of the (({Forwardable})) module in stdlib appears to be a mish-mash of two separate and incompatible examples. It begins by defining deligators for a (({RecordCollection})) class, but then goes on to make a new instance of the (({Foo})) class (never defined), calling methods on that instance that are also never defined.

Expected:
I expected it to show a new instance of the (({RecordCollection})) class and to call the methods that were delegated in the first parts of the example ((({:record_number, :size, :<<, :map}))).

=end



-- 
http://bugs.ruby-lang.org/