mirror of
https://github.com/esphome/esphome.git
synced 2026-03-01 02:14:19 -07:00
6b7258c828
The setup_priority override mechanism (struct, vector, linear scan, allocation, and cleanup) is only needed when a user explicitly sets setup_priority: in their YAML config. In practice this is almost never used - components define their priorities via C++ virtual methods instead. Gate the entire mechanism behind USE_SETUP_PRIORITY_OVERRIDE, which is only defined when the codegen encounters a setup_priority: config entry. This eliminates dead code (struct, std::vector with reserve, new/delete, linear scan in get_actual_setup_priority) from nearly all builds. Also removes the unnecessary reserve(10) call since the override count is always very small.
