> On 11 Mar 2022, at 09:28, Tim Mackinnon <[email protected]> wrote:
>
> This is really good stuff - we don't say thank you to everyone enough.
>
> Its easy to add new cool stuff... to safely fix ongoing history, and learn
> from old mistakes to create better tested solutions is really hard - and a
> testament to the durability and hard work of this community.
>
> Wow.
+100
The continued hard infrastructure work is indeed totally amazing.
Thanks you all !
> Tim
>
> On Fri, 11 Mar 2022, at 7:15 AM, Marcus Denker wrote:
>> We merged 3 PRs and fixed 4 Issue tracker entries.
>>
>> Especially #10972 is important: with this the bug that lead to an
>> overly huge image size is fixed.
>>
>> Now one can actually see that Pharo10 is smaller than Pharo9 due to:
>>
>> - code cleanup: removal of dead code, simplifications, cleanups
>> - sharing of literals across all methods as part of the image build
>> - first small improvement of size of the data structures of the code
>> (related to Protocol)
>> (much more possible here, but it has to wait for Pharo11)
>>
>>
>> There are more PRs ready for Pharo10 that just need a review to be merged:
>> https://github.com/pharo-project/pharo/pulls
>>
>>
>>
>> Fixes
>> ====
>>
>> 10667-Installed-breakpoints-not-shown-in-UI-after-AST-cache-reset-during-image-saving
>>
>> #10962
>> https://github.com/pharo-project/pharo/pull/10962
>>
>> ensure no literal is kept pinned in memory when building an image #10972
>> https://github.com/pharo-project/pharo/pull/10972
>>
>> Extend class comment of Dictionary #10973
>> https://github.com/pharo-project/pharo/pull/10973
