Contents

IT IS ALWAYS A GOOD IDEA TO WRITE A TEST!
AND ITS ALWAYS A FINE THING TO IMPROVE DOCUMENTATION!

* hash/invert: What about letting Hash#invert take a block that specifies
what to do when a collision occurs?

* hash/at_rand: allow for a _number_ of values, keys and pairs to be returned.

* > Yep. Gone. But I may replace with a version that deletes only the first 
  > matching element. Thoughts?
If you don't want to do that I would rather add an option hash to .delete and
use :once => true or something similar. (More expressive)

* numeric/bound_by: Numeric includes Comparable. Maybe drop this, but 
might it be reasonable for Numeric but no other comparables?

* nil/[]: Why should nil respond to [], but not to .each? I don't think 
nil should be treated as a container.
nil/length: See above.

* nil/method_missing: I'm not so sure about this. There is a lot of 
libraries depending on nil raising exceptions on failed method access. I 
also think that this could make programming errors very hard to find.

* fileutils/head&tail: Hm, I think the block forms ought to be equivalent to 
tail -f and so on. Then the block forms should also return all lines by default
instead of only the first 10.

* fileutils/which: Should probably be based on fileutils/where_is as they have 
lots of common code. The two methods should probably also use RUBY_PLATFORM instead
of checking for ALT_SEPARATOR.

* module/memoize: Should the main memoize method be defined as it is? 
(see bottom of file).

* kernel/demo: It can be implemented as demo "1+1"  using Binding.of_caller. 
Using only the block is possibly with SCRIPT_LINES__ or File access and is quite ugly.

* hash/weave: Document how does it compare to Hash#merge?

* Could use a better String#word_wrap method.

Version data entries

3 entries across 3 versions & 1 rubygems

Version	Path
facets-0.6.3	TODO
facets-0.7.1	TODO
facets-0.7.0	TODO