<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Build-Systems on Kuldeep Pisda</title><link>https://kdpisda.in/tag/build-systems/</link><description>Recent content in Build-Systems on Kuldeep Pisda</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 05 Oct 2026 09:00:00 +0530</lastBuildDate><atom:link href="https://kdpisda.in/tag/build-systems/index.xml" rel="self" type="application/rss+xml"/><item><title>Rust Builds Wait on Function Bodies Nobody Downstream Reads. A Patch Series Stops Waiting</title><link>https://kdpisda.in/rust-headstart-early-metadata-cargo-pipelining/</link><pubDate>Mon, 05 Oct 2026 09:00:00 +0530</pubDate><guid>https://kdpisda.in/rust-headstart-early-metadata-cargo-pipelining/</guid><description>&lt;p&gt;Cargo makes a crate wait until each of its dependencies has been fully checked, function bodies included, before it starts. But a dependent compiles against a dependency&amp;rsquo;s interface, the signatures, types and trait impls in its &lt;code&gt;.rmeta&lt;/code&gt; file. It does not need to know that the bodies type-check. A patch series published this week, &lt;a href="https://github.com/PowderworksCode/headstart"&gt;headstart&lt;/a&gt;, removes that wait for rustc and cargo, and the way it does so says a lot about what a Rust dependency edge actually carries.&lt;/p&gt;</description></item></channel></rss>