Using C11’s _Generic for Type‑Generic Macros
Learn how C11’s _Generic keyword lets you write a single type‑generic macro—illustrated with an abs() example—and understand its trade‑offs and verification steps.
Loading…
ReadMeFeed / Community knowledge
#macros
Real questions. Useful conversations. Find the people who know your stack.
Haxe Macros: Eliminate Boilerplate Without Runtime Cost
Discover how Haxe macros let you eliminate boilerplate code—like getters, setters, and serializers—without adding runtime overhead. Learn a concrete example, trade‑offs, and how to get started.
haxeUsing Crystal Macros to Generate Getter Methods
Crystal macros let you generate getter methods at compile time, keeping code DRY while preserving static type safety.
crystalDiagnosing Variable and Syntax Errors in Stata Data Pipelines
Learn how to diagnose and fix 'variable not found' and syntax errors in Stata, focusing on case-sensitivity, local macro scope, and programmatic variable confirmation.
stataBuilding Domain-Specific Languages with Racket's #lang
Stop fighting generic syntax. Learn how Racket's #lang allows you to build custom Domain-Specific Languages (DSLs) that integrate directly into the compiler.
racketCrystal Macros: Compile-Time Metaprogramming Without the Runtime Bill
Crystal replaces Ruby's runtime metaprogramming with compile-time macros. Here's how JSON::Serializable and a small getter-generating macro work, what they cost, and how to verify expansions.
Stale cache results in Haxe compilation server
Compilation Server Cache Invalidation The Haxe compilation server, utilized via --connect or --server-listen , optimizes build times by caching typed modules in memory. This mechanism relies on file paths and content hashes to determine when a module or its dependencies require re-typing. In environments utilizing generated files or complex macro-driven code
Nested #if blocks inside macros produce unexpected AST ordering
Goal: Determine how nested conditional compilation interacts with macro expansion The Haxe compiler evaluates conditional compilation directives (#if, #elseif, #else) at compile‑time, but the interaction with macro‑based transformations is not fully specified. When complex nested #if blocks are expanded by a macro, the order in which the compiler evaluates t
Crystal AOT compilation and JSON::Serializable macro: generic union type resolution across compilation units
Integration boundary Crystal's ahead-of-time compiler performs whole-program type inference while the JSON::Serializable macro expands at compile time to generate serialization code. When a generic type contains a union of concrete types that are only fully resolved after macro expansion in a separate compilation unit, the interaction between these two compi