hearth-api-reference

You can find Hearth API signatures for macro-based derivation by consulting a centralized reference that ensures alignment with current Hearth versions for accurate MIO, Expr, and Type signatures.

The correct signature for MIO.pure in Scala macro development is documented in the Hearth API reference, allowing developers to quickly verify and apply it during type class derivation tasks.

Yes, you can use this Hearth API reference to verify Expr.quote signatures during MCP checks, as it provides MCP-verified APIs for accurate reference material during library development.

Yes, the Hearth API reference includes signatures for Environment and LambdaBuilder components, alongside Expr, Type, MIO, ValDefsCache, CaseClass, and Enum, ensuring comprehensive coverage for macro work.

The best way to get up-to-date Hearth API signatures for derivation tasks is using a centralized reference that reduces time spent sifting through docs and ensures alignment with current Hearth versions.

You need a centralized Hearth API reference during Scala development when exploring Expr, Type, MIO, and LambdaBuilder APIs for macro work, documentation, or MCP verification to ensure accurate implementation.