This replaces calls to getEntryCount().hasValue() with hasProfileData
that does the same thing. This refactoring is useful to do before adding
synthetic function entry counts but also a useful cleanup IMO even
otherwise. I have used hasProfileData instead of hasRealProfileData as
David had earlier suggested since I think profile implies "real" and I
use the phrase "synthetic entry count" and not "synthetic profile count"
but I am fine calling it hasRealProfileData if you prefer.
Details
Details
Diff Detail
Diff Detail
- Build Status
Buildable 13341 Build 13341: arc lint + arc unit
Event Timeline
Comment Actions
I prefer hasProfileData to be hasRealProfileData -- unless we want to make hasProfileData to mean has real profile data and ignores synthetic entry count later.
Comment Actions
LGTM
Perhaps change the new interface documentation slightly to reflect that it is for real profile data.
Comment Actions
Expanded the comments to indicate that this returns true if entry counts from a profile run are present. Once I add synthetic counts, I can make it clear that we are looking for real counts.
Will submit with this comment change.