<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Rust on No Semicolons</title><link>https://nosemicolons.com/tags/rust/</link><description>Recent content in Rust on No Semicolons</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 18 Aug 2026 08:25:24 +0000</lastBuildDate><atom:link href="https://nosemicolons.com/tags/rust/index.xml" rel="self" type="application/rss+xml"/><item><title>The AI Code Generation WebAssembly Gap: Why Your Generated Rust Code Crashes in the Browser</title><link>https://nosemicolons.com/posts/ai-code-generation-webassembly-gap-rust-browser-crashes/</link><pubDate>Tue, 18 Aug 2026 08:25:24 +0000</pubDate><guid>https://nosemicolons.com/posts/ai-code-generation-webassembly-gap-rust-browser-crashes/</guid><description>&lt;p>Ever asked ChatGPT or GitHub Copilot to generate some Rust code for your WebAssembly project, only to watch it spectacularly fail when you try to run it in the browser? You&amp;rsquo;re definitely not alone. I&amp;rsquo;ve been there more times than I&amp;rsquo;d like to admit, staring at cryptic error messages while my beautifully generated code refuses to cooperate with the browser&amp;rsquo;s WASM runtime.&lt;/p>
&lt;p>The truth is, AI models are incredibly good at generating syntactically correct Rust code, but they often miss the subtle constraints and gotchas that come with targeting WebAssembly. It&amp;rsquo;s like having a brilliant chef who can cook amazing food but doesn&amp;rsquo;t know your kitchen only has a microwave.&lt;/p></description></item></channel></rss>