I am in the process of converting an app that has a ton of duplicated code for CIQ1 / CIQ2 / CIQ3 along with differing features (due to memory differences) into a single C-style conditionally-compiled codebase (>_>), and naturally it's tough making sure that the app is still the same for all 3 versions as it was in its previous form, especially when it comes to memory.
However, this feature request could apply to anyone with multiple versions of their app for different targets, regardless of how those versions are created (inheritance, jungles, exclude annotations, etc.). I had the same problem when I was using only exclude annotations (with duplicated code).
One thing I've noticed in the past is that when your app immediately runs out of memory because the code is too big, there's no easy way to determine the size of that code (and compare it to last working version), so you can get an idea of the impact of your code changes. In this case I use a kludge which is to build the CIQ1 code for a CIQ2 device such as 935 by editing the jungle file, so I can see the code/data size in the simulator memory viewer.
It would be nice if the memory viewer could still show you the code/data size even if the app crashed.
What would be amazing is if we could see the size of individual functions as well. (Please don't tell me there's already a way to do this....)
Thanks for reading!