BUGS & IDEAS
Issues
Report a compiler bug, a confusing error message or a missing feature. A minimal .chuchu file, your Cheeku output and your operating system make a report easy to act on.
Community · Open source · MIT licensed
Chuchu and its Cheeku compiler are young, open-source projects, and early contributors shape them the most. Report a bug, sharpen an error message, improve the docs or write code — GitHub is where it all happens.
01 · WHERE TO TAKE PART
There is no separate forum to join. The project lives on GitHub, so every conversation sits right next to the code it is about.
BUGS & IDEAS
Report a compiler bug, a confusing error message or a missing feature. A minimal .chuchu file, your Cheeku output and your operating system make a report easy to act on.
CODE
Propose a change to the language, the compiler, the docs or the website. Reviewed, tested work is merged into main.
SOURCE
All development happens in the open on GitHub under the MIT licence. Star the repository to follow progress.
02 · THE REPOSITORIES
The Chuchu language and the Cheeku compiler, written in Rust on top of LLVM.
The documentation site, covering installation, the language reference and guides.
This website, built with Next.js.
03 · CONTRIBUTING
Describe the bug or the idea first, so the approach can be agreed before you invest time in code.
Keep feature branches short-lived and focused. There are no permanent per-OS forks; everyone works from the same repository.
Formatting, tests and warnings-denied Clippy must pass before you open a pull request.
CI builds and tests the compiler natively on macOS (Apple Silicon and Intel), Linux and Windows. A failing platform is a real failure, not something to bypass.
cargo fmt --all -- --check
cargo test --locked
cargo clippy --locked --all-targets -- -D warnings04 · WRITING A GOOD REPORT