@WG-prioritization/alerts issue #78471 has been requested for prioritization.
This might be controversial, but I think
Vec::push should be inlined. So
I went through the linked PR #72227 and it seems the discussion focuses on the best tradeoff for performace and memory usage without mentioning the final binary size, so I guess the final binary size is "collateral damage" I'm not sure it can be avoided, to my (little) understanding.
By the way, I looked "non PGO Firefox builds" up. They are "non Profile-Guided Builds":
So yeah long story short :smile: I'd agree with
Vec::Push should be inlined, but we may not want to inline
Vec push. I still think that this is
P-low, though I would also be fine with
Issue #78471's prioritization request has been removed.
P-medium prefer to go with the highest possible prios :)