[auto-pr] #174: [Coding Guideline]: Defect Guideline for CERT C, INT34-C: Do not shift an expression by a negative number of bits or by greater than or equal to the number of bits that exist in the operand

[scrc-cg-pr-from-issue]

This PR was automatically generated from issue #174.

Authored by: @felix91gr

Closes #174.

[netlify]

❌ Deploy Preview for scrc-coding-guidelines failed.

Name	Link
🔨 Latest commit	f201f93
🔍 Latest deploy log	https://app.netlify.com/projects/scrc-coding-guidelines/deploys/68aa7409b0cf760008cc1805

[PLeVasseur]

@felix91gr -- could you add the new tag you're using in another PR?

Note that this fails for the same reason as over in #180, so if you addressed the tags over there, you're good.

[PLeVasseur]

Hmm... formatting issue of some type?

10:08:43 PM: /opt/build/repo/src/coding-guidelines/expressions.rst:442: CRITICAL: Unexpected section title.
10:08:43 PM: Reason 1: inconsistent behavior
10:08:43 PM: =============================== [docutils]
10:08:43 PM: /opt/build/repo/src/coding-guidelines/expressions.rst:454: WARNING: Inline strong start-string without end-string. [docutils]
10:08:43 PM: /opt/build/repo/src/coding-guidelines/expressions.rst:455: WARNING: Inline strong start-string without end-string. [docutils]
10:08:43 PM: /opt/build/repo/src/coding-guidelines/expressions.rst:456: WARNING: Inline strong start-string without end-string. [docutils]
10:08:43 PM: /opt/build/repo/src/coding-guidelines/expressions.rst:475: CRITICAL: Unexpected section title.
10:08:43 PM: Reason 2: programmer intent

Ah, I wonder if we cannot have section titles in here? I think that's probably the case.

EDIT: I'm feeling more and more like this issue is relevant 🙃
#166