I've been fascinated recently with out-of-line documentation, I was inspired by this project: https://github.com/adobe/hyde https://github.com/adobe/hyde A mor

I've been fascinated recently with out-of-line documentation, I was inspired by this project: https://github.com/adobe/hyde https://github.com/adobe/hyde A more robust implementation would parse the code to object-code, then emit a document(s) for the developer to fill in. The killer feature of such a system is that non-code changes (whitespace, etc.) would not trigger a need to re-document, but seemingly benign changes that affect distant parts of code (or a -O4 being added to the Makefile) would trigger a round of documentation