1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
//! # Heraclitus - the compiler frontend
//!
//! With heraclitus you can create your language by skipping the cumbersome lexing step
//! and using convenience parsing methods that can get you started on your language much quicker.
//!
//! The main construct that you need is the `Compiler`. The compiler will tokenize your code and assemble it
//! in a way that you can use to create AST by implementing predefined trait that helps you parse your code.
//!
//! It's pretty simple. In order to get started you need 3 steps:
//! 1. Create lexing rules
//! 2. Create your ast nodes and let them implement trait provided by this package
//! 3. Create compiler and tie all the components together
//!
//! Voilá!
//! Now you got yourself a ready to analyze / interpret / validate / compile AST.
//!
//! Ready to get started?
//! # Example
//! ```
//! use heraclitus_compiler::prelude::*;
//! # let rules = Rules::new(vec![], vec![], reg![]);
//! Compiler::new("HerbScript", rules);
//! ```
//! It is recommended to use included prelude to import just the things we will actually need.
//!
//! The `Compiler` requires lexer rules in order to exist.
//!
//! ```
//! # use heraclitus_compiler::prelude::*;
//! # fn compiler() -> Result<(), LexerError> {
//! # let rules = Rules::new(vec![], vec![], reg![]);
//! let cc = Compiler::new("HerbScript", rules);
//! let tokens = cc.tokenize()?;
//! # Ok(())
//! # }
//! ```