Yes… I make a note here and have a look sometimes the next weeks. e) is really a problem: that both source-storage and change log is the same makes things complex (but of course for the time that it was done the solution is amazingly efficient)
Marcus > On 29 Oct 2015, at 19:14, Peter Uhnák <i.uh...@gmail.com> wrote: > > yes, I already felt that test runs involving unlogged code generation is very > slow… can you add an entry on the issue tracker? > > I can, but I am not sure for what. :) > > a) speed up regular class operations (class creation, removal, compilation) > b) speed up unlogged class ops > c) modify code generation tests in Pharo (ClassTest, possibly others) to use > unlogged/suspendAllWhile > d) all of the above (as separate issues) > > plus bonus > e) create classes/methods without polluting the environment (.changes file) > (because only removal is unlogged, not creation) (if this is even possible) > > Peter