<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>const on Shepherd's Oasis</title><link>https://soasis.org/tags/const/</link><description>Recent content in const on Shepherd's Oasis</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Sun, 30 Apr 2023 00:00:00 +0000</lastBuildDate><atom:link href="https://soasis.org/tags/const/index.xml" rel="self" type="application/rss+xml"/><item><title>A Mirror for Rust: Compile-Time Reflection Report</title><link>https://soasis.org/posts/a-mirror-for-rust-a-plan-for-generic-compile-time-introspection-in-rust/</link><pubDate>Sun, 30 Apr 2023 00:00:00 +0000</pubDate><guid>https://soasis.org/posts/a-mirror-for-rust-a-plan-for-generic-compile-time-introspection-in-rust/</guid><description>&lt;p>With a powerful trait system, compile-time constants, and &lt;code>where&lt;/code>-and-&lt;code>:&lt;/code>-style bounding for types and constants, Rust&amp;rsquo;s take on generic functions has been a refreshing departure from the anything-goes, Wild Wild West, errors-only-when-called template system of C++. Furthermore, its macro system has been a much needed replacement of C&amp;rsquo;s underpowered macro system, allowing users to actually generate code in a consistent and dependable manner at compile-time, with the ever-powerful Procedural Macros (&amp;ldquo;proc macros&amp;rdquo;) taking care of some of the heaviest language extension tasks. But…&lt;/p></description></item></channel></rss>