mirror of
https://github.com/esphome/esphome.git
synced 2026-09-02 19:16:06 +00:00
J. Nick Koston
4ec2e42d4d
Rename the seven counter RMW mutators to carry the `_locked_` suffix that matches the existing convention (pop_raw_locked_, is_item_removed_locked_, cancel_item_locked_, etc.): to_add_count_increment_ -> to_add_count_increment_locked_ to_add_count_clear_ -> to_add_count_clear_locked_ defer_count_increment_ -> defer_count_increment_locked_ defer_count_clear_ -> defer_count_clear_locked_ to_remove_add_ -> to_remove_add_locked_ to_remove_decrement_ -> to_remove_decrement_locked_ to_remove_clear_ -> to_remove_clear_locked_ The caller-must-hold-lock contract became load-bearing when the underlying counters became volatile on NO_ATOMICS: ++/+=/-- compile to a three-instruction LDR/OP/STR sequence that is not atomic against a concurrent RMW from another task, so the lock is what keeps the counter consistent. The new suffix makes the requirement explicit at every call site, matching how the rest of the scheduler documents the same invariant. No behavioural change; all call sites already hold lock_.
