hearth-cross-compilation

What problem does it solve?

Cross-compiled Hearth macro development often suffers from subtle Scala 2.13 vs Scala 3 differences leading to divergent behavior, brittle code, and runtime errors.

Core Features & Use Cases

• Live reference of cross-compilation pitfalls including path-dependent types, splice isolation, type constructor matching, reification failures, Array ClassTag, upcast semantics, phantom types, and IsMap ordering.
• Guidance on safe extension loading, LambdaBuilder scope, and def-caching strategies to maintain consistent macro expansion across platforms.
• Use cases: when authoring Hearth macros or SPI extensions that must compile and run identically on both Scala 2.13 and Scala 3.

Quick Start

Review pitfalls.md first to understand common failure modes and apply the recommended extension patterns when building Hearth macros for dual-version support.