Hello all, I am interested in said project, and I'd like to ask.
Is said project limited to providing static analysis for heap allocations and file handles? To be clear I am asking whether or not there are goals beyond these two. This pattern could pretty much be used for all resource-like objects such as sockets, mutexes et cetera and point is that said problems in C++ are already tackled by using RAII <https://en.cppreference.com/w/cpp/language/raii>. Now I understand that RAII isn't always an option nor does it solve all problems (for example, dangling references) so I am still fascinated by all of it and would like to share my thoughts. C++11 mutexes(locks, and generally speaking all thread header facilities) could really use a static analyzer. Not only for the standard lock(), unlock() checks but also for "enforcing" lock ordering and other important guidelines. Read Anthony William's "Concurrency in Action" a while ago and honestly if I had a compiler that performed all those checks he describes in the book for me, which half of them I don't even remember anymore, THAT would be something else. Now I understand that this might be really complicated for a GSoC project, but food for thought. Looking forward to hearing your thoughts on this. Thanks for your time!
