<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: lumrn</title><link>https://news.ycombinator.com/user?id=lumrn</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Mon, 15 Jun 2026 04:50:57 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=lumrn" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by lumrn in "Orthodox C++ (2016)"]]></title><description><![CDATA[
<p>I’ll preface this by saying I mostly use C++ and have just basic experience in Zig, but as far as I understand comptime is much more procedural than C++ templates which are more declarative. With templates you get quite good pattern matching through the compiler’s machinery, for instance through template specialisation, while Zig, in my understanding, requires these to be handled manually in code. Personally, comptime feels like constexpr/consteval in C++ but with the ability to interact with the type system itself. The significant downside of C++ metaprogramming is that sometimes many features interact weakly and feel very much tacked on top of each other while Zig’s looks more cohesive. Perhaps someone with more Zig experience can weigh in.</p>
]]></description><pubDate>Sat, 13 Jun 2026 21:36:43 +0000</pubDate><link>https://news.ycombinator.com/item?id=48521723</link><dc:creator>lumrn</dc:creator><comments>https://news.ycombinator.com/item?id=48521723</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48521723</guid></item></channel></rss>