-
Notifications
You must be signed in to change notification settings - Fork 20
[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 #181
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
❌ Deploy Preview for scrc-coding-guidelines failed.
|
@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. |
805f1b5
to
f201f93
Compare
f201f93
to
98c3447
Compare
98c3447
to
90a32a9
Compare
90a32a9
to
9fe7d0d
Compare
There are a few things regarding the formatting that I can't quite figure out. @PLeVasseur who from the core team knows the most about Sphinx? There are a few oddities in rendering that I've noticed as I've seen the document change with the PRs, of which I can't pinpoint the cause. Stuff like some bulleted lists having a lot of spacing between their bullet and their text, to some text of the document being obscured by the page's background. So I was thinking that perhaps I could ask for help in finding the causes of those. |
(Also I'm doing the tables by hand, as you suggested :) took me a while to get to it, but I'm on it) |
Also: I just fixed a typo because CI rejected the PR due to some unrelated document having a typo. Should this be on another PR? Anywho. I'll be fixing the table on the other open PR, you tell me how we should merge the typo fix and then we can finally merge both guidelines x3 |
41a9b1d
to
9fe7d0d
Compare
Nevermind. I'll just fix that in another PR. Otherwise iterating on this one will be a pain. |
9fe7d0d
to
5bfd353
Compare
#206 has the typo fix |
6eca27f
to
e94e531
Compare
Co-authored-by: felix91gr <[email protected]> Note: tables were written by hand due to limitations in our automation
e94e531
to
7380725
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good to see this working with the manual table.
Content-wise this is good.
There's a couple of formatting snags I pointed out.
|
||
.. code-block:: rust | ||
let bits : u32 = 61; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The same indentation difference between the first line and successive lines applies here too.
|
||
.. code-block:: rust | ||
let bits : u32 = 61; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The same indentation difference between the first line and successive lines applies here too.
Well that's new 😅 Pulled from here.
|
Note: this must be addressed at the automation level, since said code blocks were generated from a GH issue
5360617
to
50f5101
Compare
I added some whitespace to the commit message @PLeVasseur, which re-triggered the Netlify deploy. However, it still errors out. So whatever is broken over there, must still be broken 🤔 |
Opened #212 to track to resolution so that we can get this build to pass. |
This PR was automatically generated from issue #174.
Authored by: @felix91gr
Closes #174.