Абмеркаванне

@vitaut you mean, in C++? I think that at first it should be vendor-specific, then they should introduce compiler options and/or pragms to choose the desired behavior, then the C++ committee should standardize it in a way that would make it easy for compiler vendors to make mistakes, and Microsoft should have a memory leak in their implementation, and then the C++ programmers should make a new "good practice" to equip their programs with a mechanism that checks whether it has been leaked, and they should use it for 20 years after Microsoft had fixed their bug, until Herb Sutter writes a blog post that it is OK not to check for memory leaks over that feature any more