http://dev.rubyonrails.org/ticket/7399 exposes a problem with Time.now.tomorrow that I personally ran into the other day. Is there a recommended way to approach this differently or is this ticket considered the "right" implementation of tomorrow, in which case I'd be more than happy to create a patch + tests.
Hmm I should clarify. The behavior is specifically this:
Date.parse('2008-03-09').tomorrow # => Mon, 10 Mar 2008 Time.parse('2008-03-09').tomorrow # => Sun Mar 09 23:00:00 -0400 2008
Apologies for the noise... looks like just a timezone setting wasn't right.
