Just wondering if this would be possible given the existing machinery of the package? i.e. the type-based analysis is helpful, but I find myself every so often in a case where there end up being a lot of potential allocations, but it's hard to pinpoint which are actually getting triggered for a certain code path. In these situations, it would be ideal to log/print out a stacktrace when an actual allocation occurred instead of a possible allocation.
Just wondering if this would be possible given the existing machinery of the package? i.e. the type-based analysis is helpful, but I find myself every so often in a case where there end up being a lot of potential allocations, but it's hard to pinpoint which are actually getting triggered for a certain code path. In these situations, it would be ideal to log/print out a stacktrace when an actual allocation occurred instead of a possible allocation.