Commit 3075ebb8 authored by POTTIER Francois's avatar POTTIER Francois

TODO.

parent e663092b
* Include BoolEqs, ChopFix.
* Include `BoolEqs`, `ChopFix`.
* Consider using two data fields in [node] instead of one,
so as to avoid using a separate [data] record. Benchmark.
* Consider using two data fields in `node` instead of one,
so as to avoid using a separate `data` record. Benchmark.
* Provide a variant of `Fix.Make` where the right-hand sides are
syntactic and come with an `eval` function? (Is it of any use?)
Use it in CFG.
Use it in `CFG`.
* Provide an API in the style of Menhir's `FixSolver`, where constraints are
discovered incrementally during a first phase, then the solver is started?
* Add `README.md` with minimal documentation.
......@@ -19,12 +22,12 @@
* Test and release the `opam` package.
* Develop a test suite. (Use afl-fuzz?)
E.g., in CFG, write a CFG generator.
Compare Fix with a naive solver.
* Develop a test suite. (Use `afl-fuzz`?)
E.g., in `CFG`, write a CFG generator.
Compare `Fix` with a naive solver.
* Develop a performance benchmark.
* If the CYK demo really is the CYK algorithm, then there should exist
* If the `CYK` demo really is the CYK algorithm, then there should exist
a formulation of it that does not have cyclic dependencies? (Otherwise
a dynamic programming solution would be impossible.) Clarify.
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment