>As an aside, compilers have used the trick of not free-ing data structures before, because it provides a significant performance boost. Instead of calling free on all those billions of tiny data structures a compiler would generate during its lifetime, they just let them leak. Since a compiler is short lived its not a problem, they get a free lunch (pun unintended), and the OS takes care of cleaning up after all is said and done. My point is that this post isn't theoretical, we do deallocation trickery in the real world.
And then someone tries to use your compiler as a service (code analysis, change triggered compiler) and it's a dead end
And then someone tries to use your compiler as a service (code analysis, change triggered compiler) and it's a dead end