Skip to content

slightly tweak description of b_list in comments #28925

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

sl4mmy
Copy link

@sl4mmy sl4mmy commented Oct 13, 2021

I noticed a small typo in the comment describing the use of b_list in
struct basicblock_ ("... that the block are allocated"). Reviewing the
other comments describing use of b_list I then noticed a slight
inconsistency in the description of what it actually points to ("next,"
"early") which I also decided to address here.

I noticed a small typo in the comment describing the use of b_list in
struct basicblock_ ("... that the block are allocated").  Reviewing the
other comments describing use of b_list I then noticed a slight
inconsistency in the description of what it actually points to ("next,"
"early") which I also decided to address here.
@the-knights-who-say-ni
Copy link

Hello, and thanks for your contribution!

I'm a bot set up to make sure that the project can legally accept this contribution by verifying everyone involved has signed the PSF contributor agreement (CLA).

Recognized GitHub username

We couldn't find a bugs.python.org (b.p.o) account corresponding to the following GitHub usernames:

@sl4mmy

This might be simply due to a missing "GitHub Name" entry in one's b.p.o account settings. This is necessary for legal reasons before we can look at this contribution. Please follow the steps outlined in the CPython devguide to rectify this issue.

You can check yourself to see if the CLA has been received.

Thanks again for the contribution, we look forward to reviewing it!

Copy link
Contributor

@MaxwellDupre MaxwellDupre left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Better.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants