Code Review (Phase 1)
I converted your lisp data into sql and made a basic web page so people can see the Proofgold Code 0.2.3 code annotated by your descriptions. Here are the four modules from your Phase 0 and Phase 1:
config: https://proofgold.org/code.php?m=1
version: https://proofgold.org/code.php?m=4
zarithint: https://proofgold.org/code.php?m=2
utils: https://proofgold.org/code.php?m=5
It's also possible to refer to a specific item:
https://proofgold.org/code.php?m=5#116
There are four modules listed in Phase 2:
json: https://proofgold.org/code.php?m=3
ser: https://proofgold.org/code.php?m=6
hashaux: https://proofgold.org/code.php?m=12
secp256k1: https://proofgold.org/code.php?m=7
I'm considering trying to crowdsource the code review, probably via memo.cash, giving out some BCH to people who look at an item, give a description and answer the basic questions (what exceptions are raised? is it tail recursive?). I can copy useful comments/answers/bug reports into sql entries so they'll be visible via the interface.
Of course, people can also join this forum and give comments and I will copy those over to sql entries as well. For people who don't mind giving their identity to github, they can also use the ai4reason github repo. I'll use comments/review/reports from there as long as I somehow end up getting access to them.
Are there any comments on this plan or the interface?
Complete thread:
- Code Review -
Brown,
2021-01-14, 16:28
- Code Review -
Brown,
2021-01-15, 10:11
- Code Review Outline - Brown, 2021-01-15, 10:12
- Code Review (Phase 0) - Brown, 2021-01-15, 19:12
- Code Review (Phase 1) -
Brown,
2021-01-16, 12:02
- Code Review (Phase 1) - BlakeKeiller, 2021-01-17, 09:26
- Code Review -
Brown,
2021-01-15, 10:11