Correct precedence issue uncovered by new warnings in v5.19.4