[Coding Guideline]: Ensure all loops have a termination condition that is provably reachable

[rcseacord]

No description provided.

[netlify]

✅ Deploy Preview for scrc-coding-guidelines ready!

Name	Link
🔨 Latest commit	aa69089
🔍 Latest deploy log	https://app.netlify.com/projects/scrc-coding-guidelines/deploys/697fdb77286d8d0008e77d5c
😎 Deploy Preview	https://deploy-preview-305--scrc-coding-guidelines.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[felix91gr]

Interesting rule. Are we sure there aren't safety-critical systems which have at least one thread that loops forever? @rcseacord

[rcseacord]

Interesting rule. Are we sure there aren't safety-critical systems which have at least one thread that loops forever? @rcseacord

@felix91gr quite possibly. the philosophy behind this rule (which is quite common in MISRA) is that this is pretty dangerous and so it should always be flagged by the analyzer. any time you have an infinite loop in your code will require a deviation permit, meaning that that infinite loops will always be scrutinized more carefully (presumably by a senior engineer who audits these things).

Presumably there aren't many of these in any given system (I would guess at most one) so the burden isn't that high.

[PLeVasseur]

@guidelines-bot /commands

[github-actions]

ℹ️ Available Commands

Pass or step away:

• @guidelines-bot /pass [reason] - Pass this review to next in queue
• @guidelines-bot /away YYYY-MM-DD [reason] - Step away from queue until a date
• @guidelines-bot /release [reason] - Release your assignment (leaves issue/PR unassigned)

Assign reviewers:

• @guidelines-bot /r? @username - Assign a specific reviewer
• @guidelines-bot /r? producers - Request the next reviewer from the queue
• @guidelines-bot /claim - Claim this review for yourself

Other:

• @guidelines-bot /label +label-name - Add a label
• @guidelines-bot /label -label-name - Remove a label
• @guidelines-bot /queue - Show current queue status
• @guidelines-bot /sync-members - Sync queue with members.md

[iglesias]

Potentially nitpicking: I thought that "relying on watchdog reset as a termination mechanism indicates a design failure" could be unnecessary.
Is using a hardware watchdog to this end really always a design failure? I do not know.

What about something else such as "relying on watchdog reset as a termination mechanism disables formal verification of system shutdown and may cause loss [...]".