Review of `util/` code

[mernst]

The Clang AST can include comments. Therefore, it is possible to determine the comment(s) immediately above a function, to do a better job of determining where comments start and end, and to obtain the specification when parsing C code with commented specifications. (This might require improvements in ParseC??)

The codebase is inconsistent in that it uses file, path, and file_path for variables of type Path.

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

• Create Plan

Examples

• Example 1
• Example 2

---

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord or schedule a call!

[vikramnitin9]

@mernst - none of this code in util/ is actually written by me, except for the C++ parsec utility (which is now a submodule). I think it might be more efficient if @jyoo980 were assigned to it, because he would be in a best place to understand the intent and structure of his own code.

[mernst]

@vikramnitin9 Thanks for the clarification. I did not understand the provenance of the code. The suggestions do still stand, though. (And maybe you can help with addressing them?? That depends on your other commitments.)