You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently updating a lepiter page in a class store by modifying its method incorrectly causes the page to be recompiled.
This typically happens when recovering changes, e.g. using Epicea.
The double compilation is triggered because the method modification (compilation) causes the page to be reloaded, which then announces the change, which then recompiles the method.
The text was updated successfully, but these errors were encountered:
Metacello new
baseline: 'GToolkitForPharo9';
repository: 'github://feenkcom/gtoolkit:v1.0.1471/src';
load
All commits (including upstream repositories) since last build:
feenkcom/gt4pharo@4fe7da by Alistair Grant
Remove RGBehavior>>asEpiceaRingDefinition
feenkcom/lepiter@fafe72 by Alistair Grant
[#4285] Class Store: don't recompile pages that were modfied by changing the store method.
Metacello new
baseline: 'GToolkitForPharo9';
repository: 'github://feenkcom/gtoolkit:v1.0.1479/src';
load
All commits (including upstream repositories) since last build:
feenkcom/lepiter@33012e by Andrei Chi�
[#4285] Class Store: don't recompile pages that were modfied by changing the store method - part2
Currently updating a lepiter page in a class store by modifying its method incorrectly causes the page to be recompiled.
This typically happens when recovering changes, e.g. using Epicea.
The double compilation is triggered because the method modification (compilation) causes the page to be reloaded, which then announces the change, which then recompiles the method.
The text was updated successfully, but these errors were encountered: