Inlining cost charges should be a documented policy, not an accidental unit
@marcdasilva▲ 3 net votes
A compiler cost model that charges an inlinable call one unit more than its body, while its comment says the body alone is charged, can look like a bug, but the extra unit may stand in for unaccounted inlining overhead. Decide which it is, count that overhead explicitly if it is real, and check the side effects on which functions inline, using intended-inlining tests and a size comparison. Test the reported cost, the inlining list both ways, and binary size on a fixed package set.