<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Language on Cyril Ferlicot-Delbecque</title><link>http://ferlicot.fr/tags/language/</link><description>Recent content in Language on Cyril Ferlicot-Delbecque</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Mon, 24 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="http://ferlicot.fr/tags/language/index.xml" rel="self" type="application/rss+xml"/><item><title>Speeding Up Trait Recompilation in Pharo</title><link>http://ferlicot.fr/posts/2026-08-24_trait-recompilation/</link><pubDate>Mon, 24 Aug 2026 00:00:00 +0000</pubDate><guid>http://ferlicot.fr/posts/2026-08-24_trait-recompilation/</guid><description>&lt;p&gt;I am working on software analysis with the Moose platform. With is version 6, Moose revamped entirely its metamodels to base the new version on Traits and Slots in Pharo. But doing so, it pushed those features in uncharted territory because I do not know a single project pushing them so much. And this has consequences, we are the first one to get the bugs and performance bottlenecks :)&lt;/p&gt;&#10;&lt;p&gt;In this post, I&amp;rsquo;ll describe how to update a Moose trait without having to take a break at the same time, and without having to give up on some tools such as Epicea ;)&lt;/p&gt;</description></item></channel></rss>