March 27, 2014
10:50 a.m.
On 27 Mar 2014, at 11:17, Johan Brichau <johan@inceptive.be> wrote:
Hi,
This is indeed something we noticed moving to Pharo3: all our benchmarks fail because of DateAndTime being slower.
?? It is slow(er) in 2 and fast(er) in 3, according to this discussion and my reading of the code. If you see the inverse, than please provide some details.
Since we use Pharo only for development, it's not a showstopper for us, but definitely an issue we are interested to help solving too.
Johan
On 26 Mar 2014, at 22:53, Stephan Eggermont <stephan@stack.nl> wrote:
DateAndTime is a very good candidate for some slot-tricks, and should probably be a value object.
Stephan