Peter Alexander: > Well, it is a little. It makes it difficult to scan code looking for GC > allocations, or even scan code looking for inefficiencies. > > Obviously I know now that I have to look for .length assignments on > arrays, but it can be quite horrific when looking at code that uses > third party libraries that you aren't familiar with.
A proposed idea to help is to add a compilation switch that produces a list of all heap allocation points in the current compilation unit (in Bugzilla there is a related issue that asks for a list of just heap allocations of closures). Bye, bearophile
