> [assertions expensive, etc] (random suggestion): Why don't we profile the cost of all assertions, or at least the number of times each is evaluated, across some some test workload.
Then we'd have a quantitative basis on which to say "we can enable the following set of assertions at the cost of a 1% perf hit, and the following extras if we are prepared to take a 5% hit". Right now it seems to me that we know assertions are expensive, but we don't have a systematic way to evaluate tradeoffs between performance and extra safety. J _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
