How accusitive/cyntax works
Project type and purpose
• This is a Rust‑based compiler toolchain (likely targeting C or a C‑like language), organized as a Cargo workspace.
• The presence of crates named cyntax_preprocessor, cyntax_lexer, cyntax_parser, cyntax_ast_lower, cyntax_hir, cyntax_consteval, cyntax_errors, and cyntax_common shows a clear pipeline from raw source to intermediate representations and error handling.
File structure
• Top‑level workspace.toml brings together multiple library crates and one binary crate (src/main.rs).
• Each cyntax_* directory is a standalone Cargo crate implementing one compilation phase or shared functionality.
• src/main.rs is the compiler driver/CLI that orchestrates all phases.
• test.c, test2.h serve as example inputs, and a tinycc directory hints at a code‑generation or integration with TinyCC.
(implicit) architecture
• There’s a linear data flow: Source files → Preprocessor → Lexer → Parser → AST Lowering → HIR → Constant Evaluator → (possibly further passes or codegen).
• cyntax_common provides shared AST definitions and utilities; cyntax_errors handles error reporting used by all phases.