Skip to content

Commit 6cea1f7

Browse files
authored
README: move progress to a dedicated issue
1 parent 60466bc commit 6cea1f7

1 file changed

Lines changed: 1 addition & 18 deletions

File tree

README.md

Lines changed: 1 addition & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -4,24 +4,7 @@ This is a human, WIP, and clean implementation of an AWK interpreter, written in
44

55
## State of the Repo
66

7-
### Lexer
8-
9-
Essentially done; it is only lacking thorough testing and numeric escapings (good first contribution).
10-
11-
### Parser
12-
13-
Also mostly done; some bullet points:
14-
15-
* Extend spans during Pratt parsing for better error messages (trivial-ish?).
16-
* The preprocessor is TBD (not complicated, but will tangle up pretty printing).
17-
* It would be nice to reduce LOC.
18-
* We are working on test coverage and fuzzing.
19-
* It's possible we move to the `chumsky` crate for this reason and `ariadne` support. I currently think it's not necessary, though; we probably are better suited to owning the parser given how idiosyncratic and ambiguous AWK's grammar is.
20-
* Start running gawk parsing tests at some point (especially when we get a basic interpreter and nail down `--pretty-print`).
21-
22-
### Interpreter
23-
24-
We are looking forward to building a basic tree-walking interpreter to get integration testing going, as well as a baseline for future iterations. Ideally, these should be a bytecode machine or a JIT. Expect this to be a fast-paced repo. The design sketch is for it to be a cooperative I/O machine, probably built with `smol`; if we want to better support AWK's long-forgotten number-crunching intent, we could easily extend this to parallel computations.
7+
Check out https://github.com/uutils/awk/issues/16.
258

269
## Contributing
2710

0 commit comments

Comments
 (0)