API reference

This site does not duplicate the exhaustive, generated signature reference — that's what Dokka is for, and it's generated directly from source on every tag, so it's never out of date with itself. What this site adds is the part Dokka can't: why a given annotation or method exists, when to reach for it, and what breaks if you don't.

How to use this section

• /modules is the curated companion reference — one page per module, every public annotation/class/function with a real example, a "why this module exists separately" section, and gotchas pulled from real source comments and issue reports.
• /recipes is task-oriented — "how do I do X," not "what does class Y expose."
• /battle-scars is where a class or method's behavior was the subject of a real, root-caused bug — worth reading before you rely on that part of the API in something that matters.
• Dokka (linked from every module and class page on this site) is the exhaustive signature source of truth — every parameter, every overload, every inherited member.

Modules