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
>
> 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 ge
Hi,
yes, I already felt that test runs involving unlogged code generation is very
slow… can you add an entry on the issue tracker?
> On 26 Oct 2015, at 13:14, Peter Uhnák wrote:
>
> Thanks Nicolai, the suspension seems to have quite a significant performance
> impact.
>
> Out of curiosity I
Thanks Nicolai, the suspension seems to have quite a significant
performance impact.
Out of curiosity I did some benchmarking. Although the numbers seems to
vary a lot based on something (the size of the image jumped from 25 to 40MB
after I was done... and there seems to be some correlation with t
Extend Pharo byte codes to support Newspeak namespaces. #justsayin
---
robert
> On Oct 24, 2015, at 6:22 PM, Nicolai Hess wrote:
>
> You can wrap the subclassing and the \removeFromSystem with
> SystemAnnouncer uniqueInstance suspendAllWhile: [ ]
>
> 2015-10-24 20:43 GMT+02:00 Peter Uhnák :
>
You can wrap the subclassing and the \removeFromSystem with
SystemAnnouncer uniqueInstance suspendAllWhile: [ ]
2015-10-24 20:43 GMT+02:00 Peter Uhnák :
> Hi,
>
> is it possible to do fast, non-system wide class subclassing in tests?
>
> Currently I would do something like
>
> ~~
Hi,
is it possible to do fast, non-system wide class subclassing in tests?
Currently I would do something like
~
MyTest>>testSomething
cls := SomeParent subclass: #Something.
"... do some tests ..."
cls removeFromSystem
