Community
Participate
Working Groups
When working on a library project, it is useful to be able to check that every function that the library declares is actually implemented somewhere. A codan checker could give a warning for a function that is declared but whose definition cannot be found anywhere in the project. This checker should probably be off by default as there are many use cases where this checking would not be desirable.
I don't know if generic checker like this really would be useful. C/C++ has tons on headers that declare lots of functions which are not defined in project you are working on. How does checker would know that this header belong to your project vs not? Even header physically located in your project it is not guarantee that it does belong to your project. Could be more heuristical approach, like header declares 10 functions, and 9 of them are defined in the same project and one is not. That probably a good reason to report this kind of issue.
We could also limit the warning to functions that are called inside the project. That increases the chances that a definition in the project is needed / the absence of a definition would produce a linker error.
