diff options
| author | Stanisław Zagórowski <hasohasacz@gmail.com> | 2024-01-14 16:42:14 +0100 |
|---|---|---|
| committer | Stanisław Zagórowski <hasohasacz@gmail.com> | 2024-01-14 16:42:14 +0100 |
| commit | dc6ab0e3e0e9d98b60f42b9e10f14013e753261a (patch) | |
| tree | 86b0f903ca3d26d9c2a58a468778883a44b6824a | |
| parent | fe7254f7a7b7c8b95824f2d6ce2ee56709ba019d (diff) | |
blog: fix structure
| -rw-r--r-- | luax/blog/building-reluax.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/luax/blog/building-reluax.md b/luax/blog/building-reluax.md index ed26c7a..72fff0d 100644 --- a/luax/blog/building-reluax.md +++ b/luax/blog/building-reluax.md @@ -108,8 +108,8 @@ experience writing a language in it from writing [brakion](https://github.com/Du and I could copy the lexer almost in full. Rust would also provide a good ecosystem for the HTTP server portion, with battle-tested libraries like [hyper](https://hyper.rs/). I didn't go for any of the higher-level libraries like [axum](https://github.com/tokio-rs/axum), since I -felt like I wouldn't really benefit from them, since what I was building was not to be a layer -on top of one, but a replacement of it. +felt like I wouldn't really benefit from them. What I was building was not to be a layer on top +of one, but a replacement of it. The parser portion took a bit, but it was not anything too complex. Writing a lexer that simultaneously structres the data, but can emit whatever garbage comes inside of an HTML tag, was |