Have you ever used a statistical analysis tool on a new large project? If you have, you must know that the first scan may produce over 1 thousand and in some cases over 10 thousand warnings. 📑 Luckily, you can control which warnings you want to work with. For example, you can limit the analysis to your project’s newest code. 👶🏻
This video describes one of the ways to do so. We call this approach mass suppression, and it is especially helpful for large projects.
Have you ever met such an abbreviation as SAST? If you have been developing for a long time, then you’re heard of it for sure. However, you might not have given it any importance. In doing so, you’re definitely wrong, because this is an incredibly important thing for the entire development process. 🦾 Today we will tell you why it is so important and how it is deciphered 🤓
If you’re using a static analyzer, most likely you stumble upon cases when it gets something wrong and gives false positives 👎 So, somehow you need to tell it about an incorrect case and let a false warning go to long rest 💤 The good news is that we have a special mechanism for this that we’ll tell you about today.
Few projects can do without outside libraries and other useful ready-made solutions. However, analyzers can see the whole code and check it with abandon. 🔎 That’s why sometimes it’s worth pointing out the spots where they should stop and analyze nothing. In this video, we’ll tell you how to do it and why it is actually useful.
Static analysis can always back you up when the time comes. But by the time it is done, you will have drunk gallons of coffee… ☕ That’s why developers of these utilities are always looking for a way to make users’ life easier and save time. ⏳ The incremental analysis became the result of this search. If you want to learn more about what it is and how it is related to a compiler, you are in the right place.