The rules behind each step are in the language reference; a guide links to the part it relies on instead of restating it. Every Turf example in these pages is compiled by CI, like the reference’s.
- Working on a Project:
turf newto a release build. Modules, formatting, diagnostics, path and git dependencies,turf.lock, CI flags, debug and release builds. - Writing a Library: the root module and what it exposes, following the standard library’s conventions, error types, generics, releasing with git tags, and wrapping a C library.
- Testing a Project: a test suite from the first assertion to CI. Fallible code, programs the compiler must refuse, panics, warnings, files, random numbers and time.
Working on the compiler itself rather than in Turf? See Contributing and Testing the Compiler.