On 30/04/2020 13:54, Raffaello Giulietti wrote:
Hi,
after more than one year after first publication, the patches [1] and
the CSR [2] are still awaiting a review...
Here's a breakdown of estimated times:
* Reading the CSR: 15-30 min. This can be done and approved
independently.
* Checking that the implementation matches the documentation [3]: 1-2
hours.
* Reading the detailed documentation: 0.5-1.0 days.
* Overall review of the code, including the extensive tests: 0.5-1.0
days.
This is impressive work. As I think was mentioned before, taking this on
would require significant review effort and long term committent to
maintain it. Has the paper been peer reviewed? Is the algorithm used by
any other languages or run-times? I know Brian Burkhalter (and maybe
Andrew Dinn too?) have put time into trying to read this but it's a
significant effort and a lot more than a few days.
-Alan
