Prismio cookbook

The cookbook answers “how do I?” questions that cross reference-page boundaries. Recipes assume Prismio 0.1.0 and state when they depend on the compiler runtime rather than an importable standard-library module.

A recipe is task-oriented: it gives a safe current approach, identifies the compiler/runtime contract involved, and calls out what remains unavailable. It does not establish new syntax or library surface.

Integration recipes

• Read command-line arguments
• Wrap a C function
• Investigate an allocation decision

Choose the right section

• Use the language reference to answer “what does this syntax mean?”
• Use the specification for conformance and exact rule boundaries.
• Use the error reference to repair a diagnostic.
• Use examples for small compiler-verified complete programs.
• Use the cookbook for an end-to-end task involving more than one rule.

Recipes stay focused and avoid inventing package or library APIs that are still Coming Soon.

Because Prismio 0.1 has no package registry — and because a resolved path dependency is not yet on the import search — several practical recipes use local extern fn wrappers. Those recipes must be read with the FFI safety boundary: symbol linking and foreign ownership cannot be proven by the Prismio compiler alone.