This is not so much an issue as an FYI. I recently found my library umm_malloc was indexed and documented by DeepWiki, and the result was actually pretty good. This is partly because I had done the work of documenting the library well, writing clear code with not too many tricky bits, and using cpputest to verify that it works :-)
I have since then found that cpputest also has a DeepWiki page, and because there is a lot of good documentation already, and the code is clear they produced a decent overview of the project, especially the sequence diagram for how tests get called.
https://deepwiki.com/cpputest/cpputest
No need for action, I just wanted to let you know it's there. I'm a bit of an AI sceptic when it comes to designing embedded systems and working on maintainable architecture. There might be something useful in the output of a documentation summary, maybe it's just that it gives an alternative perspective to good documentation that's already in place.
This is not so much an issue as an FYI. I recently found my library umm_malloc was indexed and documented by DeepWiki, and the result was actually pretty good. This is partly because I had done the work of documenting the library well, writing clear code with not too many tricky bits, and using cpputest to verify that it works :-)
I have since then found that cpputest also has a DeepWiki page, and because there is a lot of good documentation already, and the code is clear they produced a decent overview of the project, especially the sequence diagram for how tests get called.
https://deepwiki.com/cpputest/cpputest
No need for action, I just wanted to let you know it's there. I'm a bit of an AI sceptic when it comes to designing embedded systems and working on maintainable architecture. There might be something useful in the output of a documentation summary, maybe it's just that it gives an alternative perspective to good documentation that's already in place.