<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>REX Frontend Modernization on ./Code</title><link>https://blog.ouankou.com/series/rex-frontend-modernization/</link><description>Recent content in REX Frontend Modernization on ./Code</description><generator>Hugo</generator><language>en-US</language><copyright>© Anjia Wang</copyright><lastBuildDate>Sat, 16 May 2026 23:05:22 -0700</lastBuildDate><atom:link href="https://blog.ouankou.com/series/rex-frontend-modernization/index.xml" rel="self" type="application/rss+xml"/><item><title>How REX Fixed the Cxx_Grammar Timeout by Owning the Frontend Traversal Boundary</title><link>https://blog.ouankou.com/2026/05/02/how-rex-fixed-the-cxx-grammar-timeout-by-owning-the-frontend-traversal-boundary/</link><pubDate>Sat, 02 May 2026 00:00:00 +0000</pubDate><guid>https://blog.ouankou.com/2026/05/02/how-rex-fixed-the-cxx-grammar-timeout-by-owning-the-frontend-traversal-boundary/</guid><description>&lt;p&gt;Some compiler failures are loud in the right way. An assertion points at a broken parent pointer. A generated file fails to compile and the diagnostic tells you which declaration pair disagrees. A symbol lookup fails in a scope that should have owned it.&lt;/p&gt;
&lt;p&gt;Timeouts are worse.&lt;/p&gt;
&lt;p&gt;They say only that the compiler disappeared into work it could not finish before the test harness gave up. For a source-to-source compiler, that can mean many different things:&lt;/p&gt;</description></item></channel></rss>